780896 - Chrome/Safari are served a fancier Google touch site than Fennec

Status: RESOLVED WORKSFORME

(Web Compatibility :: Site Reports, defect)

Description

[Jason Smith [:jsmith]]

Currently, FF Android is getting a touch-optimized site for google.com that's acceptable and can be used sufficiently. However, webkit is still getting a better touch-optimized site. User agent sniffing is evident here to determine what content is served.

Comment 1

[Oliver Henshaw]

One of the differences is that the webkit touch-optimised site has extra search tools that pull down from the double-arrow button in the top left; in the same way the webkit classic site has the same extra search tools in the left-hand sidebar (bug 776613). Maybe these two issues have the same cause?

Comment 2

[Aaron Train [:aaronmt]]

It would be good to approach Google foremost with praise for these changes seeing as how it's taken strides to get Google to make any changes and least inquiry into the reasoning behind the content differences to see wether it was a product decision or a platform (Gecko) based decision.

Comment 3

[Oliver Henshaw]

Note: the point I was trying to make is that the "classic" site differences pre-date the recent change to the touch-optimised mobile site. So perhaps this is a pre-existing issue that now has more exposure.

Comment 4

[bug.zilla]

Hi,

is there any update to this?

Thanks

Comment 5

[Lawrence Mandel [:lmandel] (use needinfo)]

I spoke with Google a couple of months back about the list of issues that we have on file about Google Web properties. They were investigating the issues and what is required to better support Firefox. I don't have any more information at this point.

Comment 6

[bug.zilla]

One more thing to add to this: when scrolling down the list of images in Google images search results the default browser automatically loads the next images ("infinite scrolling") like the desktop results.

This does not happen with Firefox.

Comment 7

[Hallvord R. M. Steen [:hallvors]]

Looked briefly at the images.google.com search results issue - server-side sniffing (as usual with G) omits and includes CSS and some JS. The CSS sent to WebKit browsers uses some -webkit- prefixed stuff, but visually I can't see much difference. Functionally, after clicking an image one can slide through them on WebKit browsers, but need to click a small arrow in Firefox. Finally, if spoofing as the stock browser and trying to slide through the sliding works, but the rendering layers the picture sliding in on top of previous pictures - this isn't quite the intended rendering.

Comment 8

[Hallvord R. M. Steen [:hallvors]]

google.com seems quite fancy in both FxAndroid and FxOS now.

Comment 9

[Lawrence Mandel [:lmandel] (use needinfo)]

Yes it does. Looks like Firefox is now served tier 1 content for Google search. Awesome!

Comment 10

[Marco Castelluccio [:marco]]

(In reply to Hallvord R. M. Steen from comment #7)
> Looked briefly at the images.google.com search results issue - server-side
> sniffing (as usual with G) omits and includes CSS and some JS. The CSS sent
> to WebKit browsers uses some -webkit- prefixed stuff, but visually I can't
> see much difference. Functionally, after clicking an image one can slide
> through them on WebKit browsers, but need to click a small arrow in Firefox.
> Finally, if spoofing as the stock browser and trying to slide through the
> sliding works, but the rendering layers the picture sliding in on top of
> previous pictures - this isn't quite the intended rendering.

Have you filed a bug for this?

Comment 11

[Marco Castelluccio [:marco]]

I also see a different behavior for the menu in the top-left corner.

Comment 12

[Marco Castelluccio [:marco]]

Sorry for the spaghetti comments, I also see that in the images search the stock browser is served a different page that loads new images as you scroll.
There are also some other small difference in the layout (links in different places).

Comment 13

[Lawrence Mandel [:lmandel] (use needinfo)]

I don't think we should worry too much about small differences as long as they don't affect the functionality of the site. There are some other bugs filed about Google images but I don't see one that is specific to the problem that you mention in comment 12. Care to file?

Comment 14

[Marco Castelluccio [:marco]]

(In reply to Lawrence Mandel [:lmandel] from comment #13)
> I don't think we should worry too much about small differences as long as
> they don't affect the functionality of the site. There are some other bugs
> filed about Google images but I don't see one that is specific to the
> problem that you mention in comment 12. Care to file?

Filed bug 921532.

Comment 15

[Marco Castelluccio [:marco]]

(In reply to Marco Castelluccio [:marco] from comment #11)
> I also see a different behavior for the menu in the top-left corner.

Filed bug 921536.