Skip to content
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

Styling Issue on Firefox and Edge #769

Closed
blurpesec opened this issue Apr 29, 2018 · 1 comment
Closed

Styling Issue on Firefox and Edge #769

blurpesec opened this issue Apr 29, 2018 · 1 comment

Comments

@blurpesec
Copy link
Collaborator

At https://etherscamdb.info/report a styling error occurs where there is overlapping texts. This does not occur in Chrome or IE.

image

@MrLuit MrLuit added this to the 3.0.0 milestone Jun 17, 2018
@MrLuit MrLuit removed this from the 3.0.0 milestone Aug 10, 2018
@MrLuit
Copy link
Owner

MrLuit commented Aug 10, 2018

I did some research and this turned out to be Firefox and Edge handling percentages on flex containers differently from the way Chrome, Safari, and Opera are doing it. The W3C CSSWG, Microsoft, and Mozilla have recently adopted Google's behavior and such this should be fixed as of Firefox 60 (fully released as of May 9) and Edge 42.17134 (released as of April 30).

Quoting @atanassov (Edge; 24 Jan 2018):

As I stated during the WG discussion, our intention in Edge is to implement the blink and webkit behavior, i.e. resolve padding/margin-top/bottom values against the available inline size (width). Our decision is driven solely due to the compatibility issues experienced by our users.

Quoting @dholbert (Firefox; 25 Jan 2018):

We're going to change as well (away from the symmetric behavior, to the inline-axis behavior).

Sources


I'm closing this issue for now, if someone wants to add something to the discussion feel free to reopen it

@MrLuit MrLuit closed this as completed Aug 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants