We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2015-02-22 15:10:20 +0200

hzb gravatar image

Browser search highlight [Yliaavanlampi]

Having used Yliaavanlampi update for a while, I've been thinking if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

Browser search highlight [Yliaavanlampi]

Having used Yliaavanlampi update for a while, I've been thinking wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

Browser search highlight field focus behavior [Yliaavanlampi]

Having used Yliaavanlampi update for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

Browser search field focus behavior [Yliaavanlampi]

Having used Yliaavanlampi update for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

Browser search field focus behavior [Yliaavanlampi]

Having used Yliaavanlampi update (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

Browser [1.1.2.15 Yliaavanlampi] Browser: search field -- focus behavior [Yliaavanlampi]behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

[1.1.2.15 Yliaavanlampi] Browser: search field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

[1.1.2.15 [1.1.2 Yliaavanlampi] Browser: search field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

[1.1.2 Yliaavanlampi] Browser: search field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16.

[1.1.2 Yliaavanlampi] Browser: search search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16.

[1.1.2 Yliaavanlampi] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having VKB virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16.

[1.1.2 Yliaavanlampi] [since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16.1.1.2.16 and 1.1.4.x, updated the topic.

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic.

Edit 2: Still the same in 1.1.7.28.

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic.

topic. Edit 2: Still the same in 1.1.7.28.1.1.7.28. Edit 3: Still the same in 1.1.9.28 (early access).

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic. topic.

Edit 2: Still the same in 1.1.7.28. 1.1.7.28.

Edit 3: Still the same in 1.1.9.28 (early access).1.1.9.28.

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic.

Edit 2: Still the same in 1.1.7.28.

Edit 3: Still the same in 1.1.9.28.

Edit 4: Still the same in 2.0.0.10

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic.

Edit 2: Still the same in 1.1.7.28.

Edit 3: Still the same in 1.1.9.28.

Edit 4: Still the same in 2.0.0.10

Edit 5: Still the same in 2.0.1.11

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic.

Edit 2: Still the same in 1.1.7.28.

Edit 3: Still the same in 1.1.9.28.

Edit 4: Still the same in 2.0.0.10

Edit 5: Still the same in 2.0.1.11

edit 6: still the same in SFOSv2.0.2.51

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic.

Edit 2: Still the same in 1.1.7.28.

Edit 3: Still the same in 1.1.9.28.

Edit 4: Still the same in 2.0.0.10

Edit 5: Still the same in 2.0.1.11

edit 6: still the same in SFOSv2.0.2.51

update: still the same in SFOS v2.1.2.3

[since release 1.1.2] Browser: search/URL field -- focus behavior

Having used Yliaavanlampi (1.1.2.15) release for a while, I've been wondering if it would be better if the browser search field (text field) wouldn't be by default selected but required tapping before typing. It would bring more space to see all bookmark icons at glance instead of having virtual keyboard on the screen taking its space.

This could be also implemented as user-selectable setting if user prefers using search every time (so this current behaviour seems rational for them).

If you feel that it's annoying to every time close the virtual keyboard, please vote this.

Edit: Still the same in 1.1.2.16 and 1.1.4.x, updated the topic.

Edit 2: Still the same in 1.1.7.28.

Edit 3: Still the same in 1.1.9.28.

Edit 4: Still the same in 2.0.0.10

Edit 5: Still the same in 2.0.1.11

edit 6: still the same in SFOSv2.0.2.51

update: still the same in SFOS v2.1.2.3