New issue
Advanced search Search tips

Issue 822138 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug-Regression



Sign in to add a comment

word-break: break-all doesn't work on Samsung devices

Reported by stockyo...@gmail.com, Mar 15 2018

Issue description

Device name: Samsung S7 edge, Samsung S8+
Android version: 7.0, 8.0.0
WebView version (from system settings -> Apps -> Android System WebView): 65.0.3325.109
Application: Chrome
Application version: 65.0.3325.109

URLs (if applicable):
N/A

Steps to reproduce:

We have some html contents as attachment Html_Contents.txt and represent it by webview.

The html contents that include CSS word-break: break-all.

We expect the contents represented as attachment Screenshot_2.png.

But it doesn't work as attachment Screenshot_1.png on Samsung device S7 edge, S8+ with Chrome version 65.0.3325.109.

I had tried to uninstall updates on Chrome, it rolled back to factory version(S7 edge: 58.0.3029.83, S8+: 63.0.3239.111). And it worked fine as attachment Screenshot_2.png.

So, please help me to this issue, thank you.


Expected result:
word-break: break-all works.
Contents are auto fitted a phone's resolution.
See Screenshot_2.png

Actual result:
word-break: break-all doesn't work.
Contents are not auto fitted a phone's resolution.
See Screenshot_1.png

 
Html_Contents.txt
2.9 KB View Download
Screenshot_1.png
141 KB View Download
Screenshot_2.png
198 KB View Download

Comment 1 by ctzsm@chromium.org, Mar 15 2018

Cc: ctzsm@chromium.org
Labels: Needs-Feedback
stockyo827@, what's the app you are using to show this issue? Is that possible for you to provide a sample app to demonstrate the issue?

The app looks like some email app, if so, could you please send us (webviewteam [at] gmail.com) a copy of that?

Did you see this issue with other devices? Which is the latest version of WebView you see it rendered correctly?
Hi ctzsm,

Yes, it's an email app, we render user's email on Android app, and email contents from our server's email service provided by html format.
I will think how to provide a sample app for you.

I've tried other devices as below, all devices are update chrome to latest version on google play:

Represented failed on: Samsung S8+, Samsung S7 edge, Samsung SM-N910C, Huawei 9P, Sony Xperize XZ, Xiomi 6, Nexus 5X
Represented passed on: Google Nexus 6P, Sony Xperia M4, Nokia 6

And all failed devices if I uninstall updates on chrome to roll back factory version, they works passed.

I don't know which latest version rendered correctly, because only I can try is update to latest version on google play or remove update to roll back factory version. Or can you teach me how to get other version of chrome app?
If you can, I would test others to find latest version which worked fine.
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 16 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by ctzsm@chromium.org, Mar 16 2018

Labels: Needs-Feedback
stockyo827@, thank you for providing more info!

If you could provide us a sample app, we probably could bisect this issue (find the least good build). It looks like a regression, but we need a way to repro this issue so we could process, thanks!
Hi ctzsm,

I've provided a sample app as attachment.
Please reproduce the issue by this sample app, hope to help you find root cause, thanks.

WebViewSample.zip
1.6 MB Download
Project Member

Comment 6 by sheriffbot@chromium.org, Mar 20 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: aluo@chromium.org pnangunoori@chromium.org
Labels: -Type-Bug FoundIn-66 Target-67 RegressedIn-64 FoundIn-67 Needs-triage-Mobile Triaged-Mobile Target-65 FoundIn-65 Target-66 hasbisect Type-Bug-Regression
Status: Untriaged (was: Unconfirmed)
Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Install and launch the sample application provided.
2. Observed that text gets gets over flowed and user has to scroll horizontally.

Chrome versions tested:
65.0.3325.109(Stable), 67.0.3389.0(Canary)

OS:
Android 8.1.0

Android Devices:
Pixel XL

Using the per-revision bisect providing the bisect results,
Good Build - 63.0.3239.150 (508578)
Bad Build - 64.0.3240.0 (508892)

Please navigate to below link for log's and video--
go/chrome-androidlogs/822138

Unable to provide the per-revision bisect as the application gets crashed when application is launched using the builds invoked. Observed the same even after increasing the range.

@aluo -- Could you please look into this issue and provide the pre-revision bisect. 

Thanks!
Cc: ntfschr@chromium.org
Owner: aluo@chromium.org
Status: Assigned (was: Untriaged)
Assigning to aluo for per-cl bisect. If not possible, please pass back.

Comment 9 by aluo@chromium.org, May 15 2018

Owner: battun@chromium.org
battun@, could you please help to bisect this?  See comment 7 for device and Android version.
Labels: hasbisect-per-revision
Owner: chaopeng@chromium.org
Per-CL bisect information:
Good commit:508799
Bad commit:508800

Suspect CL:
https://chromium.googlesource.com/chromium/src/+/145660d6a05041e0da6a412598a29741b9efe816

chaopeng@  Might be it looks like this issue is related to your change. please look into once, if its not related to your change please reassign back to me. 

Thansk!
Hi stockyo827, I can reproduce your issue with your app.
But I can not reproduce it with the html file https://bugs.chromium.org/p/chromium/issues/attachmentText?aid=329426 with another test Webview app.

I also seeing an issue in your sample:

<meta name="viewport" content="width=device-width; initial-scale=0.75; user-scalable=1;">

viewport meta should use , not ;. So please tried with:

<meta name="viewport" content="width=device-width, initial-scale=0.75, user-scalable=1">

The CL in #10 is aimed to give a correct fallback if page give a invalid value.
chaopeng@,
Although it is not recent regression, since now we have 'per-cl bisect, marking  as RBS for now for tracking. Next week is Stable cut, so if we can get the fix before that, it would be great.

Thanks!
Labels: Needs-Feedback
Hi chaopeng

I had removed ";" on my sample code as attachment.
And the word-break still not work.
The test step and result still as Comment 2.

Thanks.

webview.zip
5.2 MB Download
stockyo827@ could you please try https://play.google.com/store/apps/details?id=com.snc.test.webview2 see if your issue is causing by any webview settings.

If you can please also share the webview app source with me.

Comment 17 Deleted

Hi chaopeng

I had shared webview app source as attachment on Comment 15.

And I had tried the app: 
https://play.google.com/store/apps/details?id=com.snc.test.webview2
And input this url:
http://ht.chaopeng.me/word-break.html

The word-break works fine.
In your attachment, I saw you still using ;

width=device-width; initial-scale=0.75; user-scalable=1

please replace all.

I can reproduce your issue on https://play.google.com/store/apps/details?id=com.snc.test.webview2 when toggle all settings same as your app. And it can fix by correcting all ,
See #11
Hi chaopeng

Sorry I didn't notice that.
I had corrected all ";" to "," then word-break works fine on my sample app.

So, should the bug fix by ourself that replace ";" to ","?
Or my webview's setting was wrong?
Status: WontFix (was: Assigned)
Yes, the issue is because you don't use correct syntax for viewport meta.

Sign in to add a comment