Update position-area support for Chrome and Firefox#28761
Merged
Elchi3 merged 2 commits intoJan 6, 2026
Conversation
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
Contributor
Author
|
Previous PR #27573 |
Elchi3
approved these changes
Jan 6, 2026
Elchi3
left a comment
Member
There was a problem hiding this comment.
Looks like the Firefox bug is marked fixed for version 148. Do you want to say so already or should we merge as is for now?
Contributor
Author
|
I'll update the PR. |
Contributor
Author
|
@Elchi3 done! |
This was referenced Jan 27, 2026
ddbeck
added a commit
to ddbeck/browser-compat-data
that referenced
this pull request
May 7, 2026
Elchi3
pushed a commit
that referenced
this pull request
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chrome has fixed its bug here. But unfortunately Firefox has the same bug.