Issue metadata
Sign in to add a comment
|
alt text isn't displayed if an element wrapping an image has a font-size of 0
Reported by
fst...@gmail.com,
Oct 31 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Steps to reproduce the problem: 1. Start Chrome 2. Load the test file (also available at: https://codepen.io/fstorr/full/LzKgGj/) 2. Disable images (chrome://settings/content/images?search=images) or, using the test file, use the "break images" link. 3. Press the Toggle Text Size button to change the size of the text in the wrapping <figure> element What is the expected behavior? alt text should always be shown What went wrong? alt text wasn't displayed Did this work before? N/A Does this work in other browsers? No Every browser apart from Edge doesn't display alt text if font-size is set to 0 on the element wrapping an image. As alt text is meant to be displayed if an image doesn't load, Edge's behavior, in displaying the alt text, improves the user experience for people in low-bandwidth areas or on pages with missing resources Chrome version: 62.0.3202.75 Channel: stable OS Version: OS X 10.13.0 Flash Version:
,
Oct 31 2017
,
Oct 31 2017
Issue 779930 has been merged into this issue.
,
Oct 31 2017
,
Nov 1 2017
Able to reproduce the issue on Windows 10, Mac 10.12.6 and Ubuntu 14.04 using reported version #62.0.3202.75 but the same is not reproducible in the latest canary #64.0.3255.0 and latest beta #63.0.3239.18. Reverse Bisect Information: ===================== Good build: 63.0.3238.0 Revision(508208) Bad Build : 63.0.3236.0 Revision(507286) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/3d78f85688013c07642ee7b8d437ba0da2f96d69..6abc19e88235609c7b8fc9df464beed2b667a773 From the above change log possible CL that fixed this issue: Change-Id: I4990ac88a9cacf1cd3e6c29a92c7f6cc3586dc3e Reviewed-on: https://chromium-review.googlesource.com/687898 robhogan@/avi@ - Could you please check and merge the fix to M62 if it is a valid candidate as the issue is not seen in M-63(beta channel). Note: Adding label ReleaseBlock-Stable as it seems to be a recent regression. ccing the reviewer of the issue as the author doesn't seem to have a chromium id. Thanks...!!
,
Nov 1 2017
,
Nov 1 2017
It isn't really suitable for merging to M62. It needs baking time in the dev chnnels. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by robdodson@chromium.org
, Oct 31 2017