Open
Bug 1423902
Opened 8 years ago
Updated 8 months ago
position relative element has height=0 in certain situation
Categories
(Core :: Layout, defect, P3)
Tracking
()
NEW
People
(Reporter: 50.ratulsaha, Unassigned)
References
Details
(Keywords: parity-chrome, parity-safari, Whiteboard: webcompat:risk-moderate )
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171112125346
Steps to reproduce:
Rendered a <img /> using base64 data.
Actual results:
Base64 image didn't render.
Expected results:
Image should have rendered correctly as it is in chromium and MS Edge.
Comment 1•8 years ago
|
||
can you provide a testcase that demonstrates the issue?
if the website is not publicly accessible, can you create a minimal testcase on jsfiddle or somewhere, or attach HTML file?
Flags: needinfo?(50.ratulsaha)
Reporter | ||
Comment 2•8 years ago
|
||
It's a React JS application. I'm isolating the component and creating a demo using that. Please wait.
Flags: needinfo?(50.ratulsaha)
Reporter | ||
Comment 3•8 years ago
|
||
(In reply to Tooru Fujisawa [:arai] from comment #1)
> can you provide a testcase that demonstrates the issue?
> if the website is not publicly accessible, can you create a minimal testcase
> on jsfiddle or somewhere, or attach HTML file?
Here is the demo
https://firefox-bug-report-1423902.netlify.com/
Steps to reproduce.
1) Click on Upload image (click me).
2) Upload image.
3) Click on upload image.
4) Full Size image show display in a pseudo popup.
Reporter | ||
Comment 4•8 years ago
|
||
(In reply to 50.ratulsaha from comment #3)
> (In reply to Tooru Fujisawa [:arai] from comment #1)
> > can you provide a testcase that demonstrates the issue?
> > if the website is not publicly accessible, can you create a minimal testcase
> > on jsfiddle or somewhere, or attach HTML file?
>
> Here is the demo
>
> https://firefox-bug-report-1423902.netlify.com/
>
> Steps to reproduce.
>
> 1) Click on Upload image (click me).
> 2) Upload image.
> 3) Click on uploaded image.
> 4) Full Size image should display in a pseudo popup.
Expected: Uploaded image should load in popup as it does in other browsers.
Actual: Image doesn't load.
Comment 5•8 years ago
|
||
thanks.
confirmed it and the issue seems to be layout or css.
Status: UNCONFIRMED → NEW
Component: ImageLib → Layout
Ever confirmed: true
Keywords: testcase-wanted
Summary: Base64 Image not getting rendered. → position relative element not getting rendered in certain situation
Updated•8 years ago
|
Summary: position relative element not getting rendered in certain situation → position relative element has height=0 in certain situation
Comment 6•8 years ago
|
||
in the testcase in comment #3, div.pdfview-wrapper has height=0
in this minimal testcase #C element has height=0.
Updated•8 years ago
|
Whiteboard: [parity-webkit][parity-chrome]
Comment 7•8 years ago
|
||
Removing the DOCTYPE makes it work, fwiw.
Updated•8 years ago
|
Priority: -- → P1
Comment 8•8 years ago
|
||
Also not that changing position of #C to static also produces zero height, while in Chrome, it produces 100%.
IIUC, position:relative element should be positioned and sized the same way as position:static when there is no top/right/bottom/left, and indeed when setting #C to have position:static, Chrome also produces 100%, so the problem here is probably how we should size a normal 100% height block (unrelated to relative), although when position is static, descendant would not be clipped.
(In reply to Mats Palmgren (:mats) from comment #7)
> Removing the DOCTYPE makes it work, fwiw.
This indicates that there is some handling which Gecko treats as quirks while other browsers accept in standard mode. That probably means we already have the code for this behavior and we just need to change its condition?
Updated•8 years ago
|
Priority: P1 → P3
![]() |
||
Comment 9•7 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome,
parity-safari
Whiteboard: [parity-webkit][parity-chrome]
Updated•3 years ago
|
Severity: normal → S3
Updated•8 months ago
|
Whiteboard: webcompat:risk-moderate
You need to log in
before you can comment on or make changes to this bug.
Description
•