A div that looks different in every browser

#1

Post by shdon » Sun, Jul 08, 2018, 12:50 PM UTC

A div that looks different in every browser
twitter.com

Re: A div that looks different in every browser

#2

Post by dopamean » Sun, Jul 08, 2018, 2:13 PM UTC

On one hand I think this is really neat. On the other this is why I have never taken front end development seriously enough to spend any real time learning it [0]. From the get go it always seemed like the rules were arbitrary and involved lots of guessing to get things right. I know this isn't actually true but it felt true enough early on to poison my mind to it.

[0] Not something I'm proud of and I know front end development is serious business so don't @ me.

Re: A div that looks different in every browser

#3

Post by webwebweb » Sun, Jul 08, 2018, 2:24 PM UTC

And GoogleBot seems to follow Safari's rendering instead of Chrome: https://developers.google.com/speed/pagespeed/insights/?url=...

Re: A div that looks different in every browser

#4

Post by JBiserkov » Sun, Jul 08, 2018, 2:47 PM UTC

Re: A div that looks different in every browser

#5

Post by Sniffnoy » Sun, Jul 08, 2018, 2:54 PM UTC

JBiserkov wrote: post #4

See also this https://mobile.twitter.com/frivoal/status/101544179390147788...

Non-mobile link: https://twitter.com/frivoal/status/1015441793901477888

Re: A div that looks different in every browser

#6

Post by crazygringo » Sun, Jul 08, 2018, 2:58 PM UTC

Is one of these correct?

Or is this combination of CSS properties ambiguously or un-defined by the spec in the first place?

Re: A div that looks different in every browser

#7

Post by bfrydl » Sun, Jul 08, 2018, 3:01 PM UTC

JBiserkov wrote: post #4

See also this https://mobile.twitter.com/frivoal/status/101544179390147788...

I think one of the most optimistic things to notice about these two images is that Edge amazingly appears to be correct in both cases.

Re: A div that looks different in every browser

#8

Post by ToFab123 » Sun, Jul 08, 2018, 3:01 PM UTC

crazygringo wrote: post #6

Is one of these correct? Or is this combination of CSS properties ambiguously or un-defined by the spec in the first place?

From the person that wrote the code: "The specs are pretty vague about how this case should be rendered, but I think Edge handles it correctly here"

Re: A div that looks different in every browser

#9

Post by adtac » Sun, Jul 08, 2018, 3:01 PM UTC

crazygringo wrote: post #6

Is one of these correct? Or is this combination of CSS properties ambiguously or un-defined by the spec in the first place?

>The specs are pretty vague about how this case should be rendered, but I think Edge handles it correctly here

Re: A div that looks different in every browser

#10

Post by moron4hire » Sun, Jul 08, 2018, 3:09 PM UTC

dopamean wrote: post #2

On one hand I think this is really neat. On the other this is why I have never taken front end development seriously enough to spend any real time learning it [0]. From the get go it always seemed like the rules were arbitrary and involved lots of guessing to get things right. I know this isn't actually true but it felt true enough early on to poison my mind to it. [0] Not something I'm proud of and I know front end…

Try writing C meant to compile in different compilers, on different processor architectures. Or ANSI SQL meant to run in a variety of RDBMSes. Web GUI is not the only bastion of arbitrary behavior.

I would wager, if your goal is to make as wide-spread, cross-platform GUI as possible, a Web GUI is the easiest way to do that, for both the developer and the users.