videolink2me.com css for chat not properly applied
Categories
(Core :: Layout: Block and Inline, defect)
Tracking
()
People
(Reporter: cfogel, Unassigned)
References
Details
Attachments
(2 files, 2 obsolete files)
Affected versions
- 76.0a1, 75.0b8, 74.0;
Affected platforms
- Windows 10, macOS 10.15;
Steps to reproduce
- Launch Firefox and access https://videolink2me.com/start
- Set up a room, join and provide the link to someone to log in as well;
- here's a link with a room we used for testing;
Expected result
- css properly set up;
Actual result
- chat elements not properly contained;
- chat input bar more specifically;
Regression range
- not a regression;
Additional information
- feel free to contact me or obotisan/asoncutean for it.
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
If I remove the contenteditable="true"
, then Chrome renders the same as Firefox. I think this is a Chrome bug where they somehow take layout decisions based on the editability of the element?
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Updated•5 years ago
|
Comment 5•5 years ago
|
||
I find it quite weird that contenteditable
affects block layout in other browsers... I see the "do what I mean" aspect of it I think...
Jonathan / Masayuki... thoughts? Should we hack block layout so that blocks that are editable at least have one non-empty line?
Comment 6•5 years ago
|
||
Meanwhile we could contact the page to add a <br>
in there I guess.
Comment 7•5 years ago
|
||
I filed https://github.com/w3c/csswg-drafts/issues/4904 and sent a message to the page authors for now.
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Guess we can keep discussing in bug 1098151. The ni? still applies :)
Comment 9•5 years ago
|
||
As I commented in the spec issue, I think that we should have a default style for it making sure accessibility for pointing device users.
Updated•5 years ago
|
Updated•4 years ago
|
Description
•