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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add dialog light dismiss behavior #10737
base: main
Are you sure you want to change the base?
Add dialog light dismiss behavior #10737
Changes from 1 commit
4a93ad6
3630019
32c2240
78f9789
b99c5ac
8698d0b
f50198e
fb01762
4f205bd
38bdafe
873e451
e7fbbec
8b019a4
b57968e
ea474af
db56191
82a4561
6a9e20b
20dc2fe
f5a0919
3f413d3
d9ed19f
ff98f98
2fb87b1
6aa7386
344d87f
76619aa
57df925
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this assert fails if you do
#10124 will fix this, but I'm hesitant to block this PR on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, you're right. The Chromium code has to work around the state of that feature flag.
Since that PR "fixes" the behavior for removing the
open
attribute, would you be ok with me just removing thisAssert
, rather than trying to bring in much of that PR?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, as long as you can verify the assert is not load-bearing, then just removing it for now seems reasonable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it's load bearing in the case you bring up above - removing the
open
attribute. But the spec isn't super clear about that now anyway, so I guess it only bears code-implementation weight, not spec weight. LMK if that makes sense.