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

[Bug] Google search website broken [released]

Tracked by Jolla (In release)

asked 2019-05-06 17:08:03 +0300

Alex gravatar image

updated 2019-05-06 17:39:16 +0300

jovirkku gravatar image


Since the SFOS update the Google search website bar is broken in the native browser and it is not possible to select another search category (e.g. pictures) after the initial search.

This affects the german website whereas the american website seems to be working as expected.

Affected devices and versions

This issue was introduced with SFOS on my Sony Xperia XA2 Dual-Sim device.

How to reproduce

  1. Open the german Google website Google.de in the native browser
  2. Search for e.g. 'Sailfish OS'
  3. Result: The top search bar is broken. The clear button for deleting the search key is displayed in front of the search categories and it is not possible to select any of categories (e.g. pictues, videos).

image description

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by Alex
close date 2019-10-31 21:37:04.937996



Looks familiar, I can confirm this behaviour.

goldenm ( 2019-05-06 20:28:54 +0300 )edit

2 Answers

Sort by » oldest newest most voted

answered 2019-05-06 21:35:26 +0300

rainemak gravatar image

updated 2019-05-06 21:36:25 +0300

Here's a PR for fixing the issue: https://github.com/sailfishos/sailfish-browser/pull/628 -- not full top level domain list.

There's no need to update browser rather you'll get the update over the air approx. in two days after integrated.

For your interest: https://sailfishos.org/wiki/Sailfish_OS_Cheat_Sheet#Debugging_User-Agent_problems

edit flag offensive delete publish link more


Great thanks for the fast reply and the PR. :)

Alex ( 2019-05-06 22:28:09 +0300 )edit

@rainemak@jovirkku This bug is declared as fixed in the release notes of SFOS 3.1.0 but it is actually not fixed in the EA release

Alex ( 2019-07-22 22:49:40 +0300 )edit

Hi @Alex these user-agent fixes are not bound to release version even though there's an entry in the release notes. User-agent fixes are deployed over the air while using the browser and are checked every second day.

If you have access to the device maybe you could check the last update time stamp (chop of two digits from the end):

[nemo@Sailfish ~]$ grep lastupdated .mozilla/mozembed/prefs.js
user_pref("general.useragent.updates.lastupdated", "1563379563755");
[nemo@Sailfish ~]$ date -d @1563379563
rainemak ( 2019-07-23 08:43:55 +0300 )edit

@rainemak The user-agent has been updated on 22nd July, but there are no changes in my browser and the issue persists.

Alex ( 2019-07-23 08:55:57 +0300 )edit

Then let's check to output of the ua.update.json itself:

[nemo@Sailfish ~]$ cut -c 4708-4819 .mozilla/mozembed/ua-update.json
rainemak ( 2019-07-23 09:06:36 +0300 )edit

answered 2019-05-06 20:54:33 +0300

bocephus gravatar image

Google is evil and should be avoided at all costs.

Use https://duckduckgo.com/ , https://www.startpage.com/ or similar.

edit flag offensive delete publish link more

Question tools



Asked: 2019-05-06 17:08:03 +0300

Seen: 341 times

Last updated: May 06 '19