Status Update
No update yet.
Comments
ka...@google.com
Tried to reproduce the issue on chrome version #131.0.6778.85 using Mac 14.7.1 as per
Steps to reproduce:
---------------------------
1. Launched chrome browser
2. Opened the link "https://codepen.io/asuh/pen/PoMJYvp?editors=1100 "
3. Hovered the option link seen crash error
4. Clicked on toggle device toolbar and choose option menu and clicked on home seen same error as above
Note:-1)For regression range followed same steps in older builds M-121, observed no web share feature is supported
2)The feature is implemented fromM-129 Observed different behaviour no error
3) Also followed steps in firefox seen same behaviour as in M-129
Attaching screencasts and screenshots for reference
Reporter@ Could you please review the attached screencasts and screenshots and let us know if anything being missed here and please confirm if this is the issue you are pointing to? and also confirm M-129 behaviour is bad?
Thanks..!!
Steps to reproduce:
---------------------------
1. Launched chrome browser
2. Opened the link "
3. Hovered the option link seen crash error
4. Clicked on toggle device toolbar and choose option menu and clicked on home seen same error as above
Note:-1)For regression range followed same steps in older builds M-121, observed no web share feature is supported
2)The feature is implemented fromM-129 Observed different behaviour no error
3) Also followed steps in firefox seen same behaviour as in M-129
Attaching screencasts and screenshots for reference
Reporter@ Could you please review the attached screencasts and screenshots and let us know if anything being missed here and please confirm if this is the issue you are pointing to? and also confirm M-129 behaviour is bad?
Thanks..!!
mi...@gmail.com
Thanks for the review. I confirm your recordings and screenshots to be what I experience as well. Thanks
pe...@google.com
Thank you for providing more feedback. Adding the requester to the CC list.
ka...@google.com
Able to reproduce the issue on chrome version #131.0.6778.86 with the sample URL provided in
Observed crash error while hovering
Note: Issue not seen in firefox
Reproducible on:
-----------------------
131.0.6778.86 - Stable
132.0.6834.15 - Beta
133.0.6847.2 - Dev
133.0.6860.0 - Canary
Bisect Information:
-------------------------
Good Build: 129.0.6641.0
Bad Build : 129.0.6642.0
Bisect Script : python3 bisect_builds.py -o -a mac -g 129.0.6641.0 -b 129.0.6642.0
Change Log : "https://chromium.googlesource.com/chromium/src/+log/c20ba57087f147b22a78a0fd916fdc4b887c2946..36e8cecee4e2b221a8117f330567f91cd65532c5 "
Suspect : "https://chromium.googlesource.com/chromium/src/+/36e8cecee4e2b221a8117f330567f91cd65532c5 "
Change-Id: Id2a7edc81837eed6746f1dad93d22ca7208ff4f6
Reviewed-on:https://chromium-review.googlesource.com/c/chromium/src/+/5766813
Mason Freed@ Please help in re-assigning if this is not related to your change.
Thanks..!
Observed crash error while hovering
Note: Issue not seen in firefox
Reproducible on:
-----------------------
131.0.6778.86 - Stable
132.0.6834.15 - Beta
133.0.6847.2 - Dev
133.0.6860.0 - Canary
Bisect Information:
-------------------------
Good Build: 129.0.6641.0
Bad Build : 129.0.6642.0
Bisect Script : python3 bisect_builds.py -o -a mac -g 129.0.6641.0 -b 129.0.6642.0
Change Log : "
Suspect : "
Change-Id: Id2a7edc81837eed6746f1dad93d22ca7208ff4f6
Reviewed-on:
Mason Freed@ Please help in re-assigning if this is not related to your change.
Thanks..!
fu...@chromium.org
ap...@google.com
Project: chromium/src
Branch: main
Author: Rune Lillesveen <
Link:
TransformPositionArea() incorrectly assumed two-value input
Expand for full commit details
TransformPositionArea() incorrectly assumed two-value input
Crashed when input was not a pair, but assumed it would be.
For logical values like position-area:start, we can store the value as
a single keyword, but the flip-block version of it needs to be two
separate values.
position-area might be represented as a single keyword depending on
which it is, but it's irrelevant whether the non-flipped value was a
single keyword or two keywords. For simplicity keep identical values.
Bug: 380321441
Change-Id: I29b91e7cc6dd7bea286f11475382117afb872377
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6063638
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1390298}
Files:
- M
third_party/blink/renderer/core/css/try_value_flips.cc - A
third_party/blink/web_tests/external/wpt/css/css-anchor-position/chrome-380321441-crash.html
Hash: add0e4082ad9557729f1c294c040535bca499c0a
Date: Mon Dec 02 14:37:07 2024
fu...@chromium.org
ka...@google.com
Verified the fix on the latest canary M133#133.0.6874.0. using Linux debian, Mac 14.7.1, Win 10 as per
Observed no crash
Note:-While hovering the popup is seen below the home button but in withfix build the pop up is seen in the middle of the page
Hence, the fix is working as expected and adding verified labels
Attaching screencast for reference
Thanks..!!
Observed no crash
Note:-While hovering the popup is seen below the home button but in withfix build the pop up is seen in the middle of the page
Hence, the fix is working as expected and adding verified labels
Attaching screencast for reference
Thanks..!!
Description
Steps to reproduce the problem
Problem Description
I was implementing anchor positioning and popovers to work together, and I ran into an issue where hovering the cursor over a link that's associated with a popover via anchor positioning causes the page to throw an error. I'm not sure if this is bubbling up because a similar error is generated if I decrease the viewport width of the iframe rendering the markup and the hover over a mobile-only button that says "Menu".
Summary
Anchor positioning + popover bug
Custom Questions
Which component does this fall under?
Blink>CSS
Does this work in other browsers?
Yes - This is just a Chrome problem
Additional Data
Category: API
Chrome Channel: Stable
Regression: N/A