google.com News search on Firefox for Android: news titles contain extra linebreaks
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:6, firefox147 verified)
| Tracking | Status | |
|---|---|---|
| firefox147 | --- | verified |
People
(Reporter: mstange, Unassigned)
References
()
Details
(Keywords: webcompat:contact-complete, webcompat:site-report, Whiteboard: [webcompat:sightline][webcompat:japan])
User Story
platform:android impact:annoyance configuration:general affects:all branch:release user-impact-score:300
Attachments
(2 files)
This was originally reported in https://www.reddit.com/r/firefox/comments/1dukx2t/another_reason_why_google_is_evil/ and I can reproduce it.
Steps to reproduce:
- In Firefox Nightly for Android, do a google search for the string "android".
- Switch to the "News" tab.
Expected results:
The titles of the news in the top list should have reasonable line breaks.
Actual results:
In each result, there's a line break after the first word and second word of the title.
Chrome:
You could get a cut of Google's
$700 million lawsuit payout if you
own an Android
Firefox:
You
could
get a cut of Google's $700 milli...
Looking at the DOM of the page in the devtools inspector, there is a <br> after "You" and after "could".
| Reporter | ||
Comment 1•1 year ago
|
||
Comment 2•1 year ago
|
||
Add a ni for Dennis to reach out to Google
Comment 3•1 year ago
|
||
These <br> tags aren't there in Chrome, so this isn't a rendering difference or anything. I've reached out to them.
Comment 4•1 year ago
|
||
It doesn't look like we need to do any diagnosis here, so removing that flag for now.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
•
|
||
As one additional data-point: you can see this bug reproducing in the Firefox screenshots on https://github.com/webcompat/web-bugs/issues/141292 (though that particular github issue was focused on something else -- an unexpected left-vs-right ordering of text & images that the reporter was seeing -- and that issue was closed because that part wasn't reproducible).
Comment 7•1 year ago
|
||
(In reply to Dennis Schubert [:denschub][OOO - back Jan 7th] from comment #3)
I've reached out to them.
I'm not sure we ever heard back from this outreach, so I followed up on the email thread today.
Comment 8•1 year ago
|
||
The severity field for this bug is set to S4. However, the following bug duplicate has higher severity:
- Bug 1938058: S3
:ksenia, could you consider increasing the severity of this bug to S3?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•11 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Comment 10•3 months ago
•
|
||
As chatted in the webcompat channel, I am removing the keyword from webcompat:site-wait. Keeping webcompat:contact-in-progress should be enough.
Comment 11•2 months ago
|
||
I have filed b/467804205 to track this within Google.
Comment 12•1 month ago
|
||
We believe we've identified the root cause and will be deploying a fix soon.
Comment 13•1 month ago
|
||
This should now be fixed, please verify on your end and let us know if you still see any issues.
Comment 14•1 month ago
|
||
Yes, this looks fixed on my end. Thank you!
Comment 15•1 month ago
|
||
Verified, the issue no longer reproduces.
Tested with:
- Browser / Version: Fenix 147.0-candidate build 1
- Operating System: Google Pixel 5 (Android 14)
Updated•1 month ago
|
Description
•