Resizable DOM element shows a resizer in fullscreen mode, but it can't be resized
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: 003mjf, Unassigned)
Details
Attachments
(1 file)
|
593 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36
Steps to reproduce:
- Open the attached HTML file.
- Click the "Enter/Exit Fullscreen" button.
Actual results:
When the "container" div enters fullscreen, the resizer still shows but can't be resized.
Expected results:
The resizer will be hidden in fullscreen mode.
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•5 years ago
|
||
Although it's same behavior as Chrome and not sure how spec defines this, but I also feel it's odd to show resizer in fullscreen.
I'm not sure who maintains fullscreen mode now. Especially, this might be a layout issue. Emilio?
|
||
Comment 3•5 years ago
|
||
Yeah, I don't think it's well defined, and not sure how much sense it makes to do special-case and fix it on the Gecko side... Authors can trivially fix it by using:
#container:fullscreen { resize: none }
In the example above. Maybe resize: none !important should be in https://fullscreen.spec.whatwg.org/#user-agent-level-style-sheet-defaults? Unclear.
|
Reporter | |
Comment 4•5 years ago
|
||
Thanks for the reply. Should we need to create a new issue in https://github.com/whatwg/fullscreen/issues?
I'm trying to make a patch to change layout&paint behavior in Chromium code, but Emilio's idea is better.
|
|
||
Comment 5•5 years ago
|
||
Yes, I think that'd be a sensible request for the spec. I think we should close this as worksforme meanwhile, as there's a solution, and I don't think a special-case in layout is warranted for this.
If the spec adds it, we can file another bug to add :fullscreen { resize: none !important } or such.
Description
•