Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A div that looks different in every browser

twitter.com

Post reply on HN
Print view View original

31–40 of 133 posts

Re: A div that looks different in every browser

#31

Post by jayd16 »

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…

This isn't really a spec thing. Its more a manifestation of undefined behavior. Even c++ compilers have undefined behavior.

Re: A div that looks different in every browser

#32

Post by lisper »

evan_ wrote: post #29
mvdwoord wrote: post #28

Earlier quoted context omitted.

What is the status quo on vertical alignment if I may ask..

Flex box https://philipwalton.github.io/solved-by-flexbox/demos/verti...

The code shown on that page actually doesn't work, though the code in the github repo does.

And this exposes the problem with the current state of the art: yes, you can probably get flexbox to do what you want [@] if you know how. But if you don't know how, trying to figure it out is still very hard. You should be able to write:

    stuff
or

    stuff
There is really no reason that should not Just Work. (The tag has worked for 20 years, notwithstanding that it has been deprecated for most of that time.)

---

[@] What if I want to put something in the lower left or upper right hand corner?

Re: A div that looks different in every browser

#33

Post by kevingadd »

Operyl wrote: post #23
webwebweb wrote: post #3

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

I wonder if that’s because they’re just running an older version of WebKit/blink.

"Chrome's" rendering in many cases is going to be whatever hardware accelerated stack (probably Skia + your platform's particular hardware API) is rasterizing the page. Headless rendering as found in a page scraper bot is more likely to be using software rasterization and might be using an entirely different API. Chrome has a few command line flags that can push everything through different rendering paths and you can get different results from it.

Re: A div that looks different in every browser

#34

Post by dredmorbius »

mvdwoord wrote: post #28
robbrown451 wrote: post #25

Earlier quoted context omitted.

Honestly its getting rarer and rarer to find things like this, most things that reasonable people want to do "just work." You have to go to considerable effort to come up with a case like this.

What is the status quo on vertical alignment if I may ask..

Grid or flex.

Re: A div that looks different in every browser

#35

Post by bryanrasmussen »

amelius wrote: post #12
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…

> 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. I guess you aren't into Deep Learning either ;)

Most programming/development environments/standards have arbitrary rules. Also most workplaces I've found.

It's arbitrary almost all the way down.

Re: A div that looks different in every browser

#38

Post by tgummerer »

jayd16 wrote: post #31
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…

This isn't really a spec thing. Its more a manifestation of undefined behavior. Even c++ compilers have undefined behavior.

Especially C++ compilers have undefined behavior

Re: A div that looks different in every browser

#39

Post by krsdcbl »

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…

So you're saying other dev domains don't have intrinsic glitches and oddities? ;)

Re: A div that looks different in every browser

#40

Post by rvense »

lisper wrote: post #32
evan_ wrote: post #29

Earlier quoted context omitted.

Flex box https://philipwalton.github.io/solved-by-flexbox/demos/verti...

The code shown on that page actually doesn't work, though the code in the github repo does. And this exposes the problem with the current state of the art: yes, you can probably get flexbox to do what you want [@] if you know how. But if you don't know how, trying to figure it out is still very hard. You should be able to write: stuff or stuff There is really no reason that should not Just Work. (The tag has worked f…

You should not be centering things in HTML, that's the stylesheet's job.
Post reply on HN