demo.lubelogger.com - Height of the table cells is not rendered correctly
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(Webcompat Priority:P3, Webcompat Score:3)
People
(Reporter: ctanase, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux,android impact:significant-visual configuration:general affects:all branch:release diagnosis-team:layout user-impact-score:40
Attachments
(2 files)
Environment:
Operating system: Windows 10
Firefox version: Firefox 131.0.2/133
Preconditions:
- Login Credentials:
username: test
password: 1234
Steps to reproduce:
- Go to https://demo.lubelogger.com
- Log in with the credentials provided in preconditions.
- Access the calendar.
- Observe the table cells.
Expected Behavior:
The height of the table cells is normal.
Actual Behavior:
The height of the table cells is small.
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in Firefox Nightly, and Firefox Release
- Does not reproduce in Chrome
Created from https://github.com/webcompat/web-bugs/issues/142655
| Reporter | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Comment 2•1 year ago
|
||
This looks like a version of bug 1461852.
The website has height:20px on the td elements, and Firefox is dutifully honoring that specified height. If I uncheck that declaration, then Firefox uses a larger height for the td elements to fill the table's height.
Comment 3•1 year ago
•
|
||
Here's a reduced testcase (from testcase-reducer) just in case the site happens to change or become inaccessible due to e.g. testing login-credentials being removed, and we want to circle back to confirm wehther the original behavior was fixed or not, e.g. after fixing bug 1461852 at some point in the future.
(I suggested a workaround over on github in case the site developer wants to work around this, too, so it's possible this will become unreproducible on the original site for that reason.)
Comment 4•1 year ago
|
||
After poking a bit more, I realized this is a distinct issue from bug 1461852 and I spun off bug 1929173 for it.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•11 months ago
|
Description
•