br + a in table cell is not correctly positioned
Reported by
shiba200...@gmail.com,
Oct 26 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.18 Safari/537.36 Example URL: https://jsfiddle.net/xl1blue/ywsg9tgb/4/ Steps to reproduce the problem: 1. Open https://jsfiddle.net/xl1blue/ywsg9tgb/4/ 2. Click "test" link 3. The link does not work. The right cell will shorten as the screenshot below 4. If I click "test" again, this link works (navigates to example.com) What is the expected behavior? The link should navigate me to example.com The table should keep rectangle What went wrong? https://gyazo.com/a65bf60b82bb12c8bea66928a74cbe4f Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 63.0.3239.18 Channel: dev OS Version: 10.0 Flash Version:
,
Oct 27 2017
Able to reproduce the issue on the latest canary(64.0.3251.0) and the latest dev(63.0.3239.18) on Windows-10, Mac OS 10.12.6 and Liunx Ubuntu 14.04. Regressed in M-63. Last good build: 63.0.3231.0 First bad build: 63.0.3232.0 Changelog: ========== https://chromium.googlesource.com/chromium/src/+log/dd160677bc6cd8a5ab468c187f61902a8fbf4b41..818f2935aba99b00716f8ab2804c211d99c39f31 robhogan@: Could you please take a look at this. Thank you!
,
Oct 27 2017
,
Oct 27 2017
We should probably revert on trunk and 63 rather than merging the fix to 63. Proceeding...
,
Oct 30 2017
[Bulk Edit] URGENT - PTAL. M63 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP. Thank you.
,
Oct 30 2017
Rob, are you fine with dgrogans suggestion or is the fix safe to merge into 63?
,
Oct 30 2017
I reverted on trunk on friday in https://chromium-review.googlesource.com/c/chromium/src/+/742362. Looks like the bug the CL in question fixed ( issue 768330 ) wasn't a regression so I will merge the revert to 63, assuming that the revert actually fixed this bug's issue. Even if Rob can come up with a fix quickly (and I wouldn't be surprised!) I want that fix to have a full cycle of testing.
,
Oct 30 2017
Re #7, pls request a merge to M63 by applying "merge-request-63" label. Hoping it will be a safe revert merge.
,
Oct 30 2017
Thanks David.
,
Oct 30 2017
Request to merge https://crrev.com/c43a08fc7d2b3a2e3fb8ead1dcfc931ec3b5cd41 Tested yesterday's canary, which has the revert, and the bug reported here was fixed.
,
Oct 30 2017
This bug requires manual review: M63 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), gkihumba@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 30 2017
Approving merge to M63 branch 3239 based on comment #10. Please merge ASAP. Thank you.
,
Oct 30 2017
,
Oct 31 2017
If nothing is pending for M63, please apply "merge-merged-3239" label and remove "Merge-Approved-63" label. Thank you.
,
Oct 31 2017
,
Oct 31 2017
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by chrishtr@chromium.org
, Oct 26 2017