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 2013-12-25 13:55:20 +0200

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

According to the changelog the upgrade to 1.0.2.5 fixes this issue - everyone please confirm that you don't see this bug on 1.0.2.5

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

According to the changelog the upgrade to many people who provided feedback here, 1.0.2.5 fixes this issue - everyone please confirm that you don't see this bug on 1.0.2.5does NOT fix this.

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

According to many people who provided feedback here, 1.0.2.5 does NOT fix this.

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

According to many people who provided feedback here, 1.0.2.5 does NOT fix this.

EDIT 2014-02-03: After 1.0.3.8 do others also still get this bug?

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

According to many people who provided feedback here, 1.0.2.5 does NOT fix this.

EDIT 2014-02-03: After 1.0.3.8 do others also still get this bug?

Bug: sometimes the browser gets into a state when all links are unclickable

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

According Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this.this

EDIT 2014-02-03: After 1.0.3.8 do others also 4.2.2014 many reports confirm that the bug is still get this bug?present in 1.0.3.8

Bug: sometimes the browser Browser occasionally gets into a state when all links are unclickablewhere pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

Bug: Browser occasionally gets into a state where pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

Bug: Browser occasionally gets into a state where pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

Bug: Browser occasionally gets into a state where pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

EDIT 20.0.4.2014 added 1.0.5.16 tag as reproduced on this build too

Bug: Browser occasionally gets into a state where pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

EDIT 20.0.4.2014 added 1.0.5.16 tag as reproduced on this build too

**EDIT 12.06.2014 added 1.0.7.17 tag as reproduced on this build too

Bug: Browser occasionally gets into a state where pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

EDIT 20.0.4.2014 added 1.0.5.16 tag as reproduced on this build too

**EDIT 12.06.2014 EDIT 12.06.2014 added 1.0.7.17 tag as reproduced on this build too

EDIT 21.01.2015 is this still applicable to 1.1.1.27 can anyone reproduce?

Bug: Browser occasionally gets into a state where pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

EDIT 20.0.4.2014 added 1.0.5.16 tag as reproduced on this build too

EDIT 12.06.2014 added 1.0.7.17 tag as reproduced on this build too

EDIT 21.01.2015 is this still applicable to 1.1.1.27 can anyone reproduce?

EDIT 02/10/2018 this is also applicable to 2.2.1.18 - For example eBay mobile pages, fine to begin with, but page/s get slower and slower scroll/select options from menus/click links like 'Mark as dispatched', etc.

Bug: Browser occasionally gets into a state where pages don't accept any touch input.

I don't know how to reproduce this but sometimes the browser gets into a state when nothing happens when I click on any of the links. When this happens, switching between tabs or reloading the page doesn't help - the only way to workaround it is to close the browser app and open it again.

Edit 1 according to many people who provided feedback here, 1.0.2.5 does NOT fix this

EDIT 4.2.2014 many reports confirm that the bug is still present in 1.0.3.8

EDIT 20.0.4.2014 added 1.0.5.16 tag as reproduced on this build too

EDIT 12.06.2014 added 1.0.7.17 tag as reproduced on this build too

EDIT 21.01.2015 is this still applicable to 1.1.1.27 can anyone reproduce?

EDIT 02/10/2018 02.10.2018 this is also applicable to 2.2.1.18 - For example eBay mobile pages, fine to begin with, but page/s get slower and slower scroll/select options from menus/click links like 'Mark as dispatched', etc.