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

111–120 of 133 posts

Re: A div that looks different in every browser

#111

Post by sonnyblarney »

randomsearch wrote: post #93
sonnyblarney wrote: post #58

Earlier quoted context omitted.

" I know this isn't actually true " It's true. A confluence of vague definitions, poor implementations, bad documentation ... and this is the web we have. It's the tip of the iceberg, and the painful life of anyone doing html5 work, it's 'not fun' for anyone who's been exposed to regular programming because the problems you spend your day solving mostly should not be problems to begin with.

I agree. I recently started learning front end development. My reaction after grasping what modern frameworks do is “my god, what have we done?” It seems like we’ve expended a huge amount of effort to hack the web into something we can build SPAs in (and what an insightful TLA that is). I wonder if this sort of situation was inevitable or, given sufficient coordination and standardisation, we could have built a bette…

"How much did graphic designers, UX experts, psychologists etc impact the evolution of the web standards?"

They didn't. It's just a mess.

We want to believe there is genius in the commons, but really I don't think there is a lot of coherence. It's just some small group thought it would be good to do this or that, and it made sense at the time.

Re: A div that looks different in every browser

#113

Post by jhomedall »

pjmlp wrote: post #86
shawn wrote: post #62

Earlier quoted context omitted.

This is what us older people would like to believe. Meanwhile the young webdevs are having a blast ignoring us and building the apps of the future.

Yeah and then they all jump around React as some amazing achievement, having rediscovereed how 90's native UI do event handling.

React isn't really anything like 90s UI libraries. It is, however, very much like the fairly recent native immediate-mode GUIs that have come out (https://github.com/ocornut/imgui, https://github.com/PistonDevelopers/conrod, etc).

The core feature of React is that your UI is a pure function of your application state. In (e.g.) the Win32 UI, you would receive events, and then need to manually transition your current UI state to the new UI state (hide this button, disable this input, etc).

Re: A div that looks different in every browser

#114

Post by gedy »

Dylan16807 wrote: post #108
gedy wrote: post #63

Earlier quoted context omitted.

Sure, because "vertically centered" means relative to what?

I want the contents of my div to be centered inside my div. Just like works, but vertically. You don't need content for horizontal centering. I consider it a layering violation to have to do that nesting.

Maybe we are misunderstanding each other, but while you don't need an "extra" container, you do need a container with some known height to vertically center the content in: http://jsfiddle.net/c20gq4pz/

Re: A div that looks different in every browser

#115

Post by nadsumatal »

Joke: A man walks into a picture framing shop and says: "I'd like a 10cmx10xm frame for my 10cmx10cm picture, but make it negative 12.5cm away from the picture." The shop staff is confused, but makes a wild guess: "So you want a frame with each border 2.5cm on the other side of the picture than it would normally be?" The man just takes a note and goes to another shop.

He collected the wild guesses from various picture framing shops and posted them on twitter, getting a lot of attention on Hacker News as well.

edit: present tense.

Re: A div that looks different in every browser

#116

Post by talmand »

lisper wrote: post #71
howdydoo wrote: post #67

Earlier quoted context omitted.

https://codepen.io/anon/pen/NzQQJm This is a gross abuse of html, but if you really want that syntax, you can have it. I can't say I understand all the complaining here. You want to make $200K a year sitting at a desk, but learning flexbox or googling when you need it is too much effort?

Your code breaks the tag: if you try to nest a inside your it doesn't work. And my complaint is that I believe that computing should be accessible to everyone, and that simple things should not be made difficult just so that an elite guild can command above-market wages to fix problems that they themselves created. I don't believe in broken-windows economics.

Wait, front-end developers who use CSS created the problems of CSS? That's really funny. I mean, that's the most mind-blowing accusation I've heard in a long time. I would have to suggest you are commenting on a topic that you actually know very little about.

But at least you are entertaining.

Re: A div that looks different in every browser

#117

Post by kevingadd »

bla2 wrote: post #55
kevingadd wrote: post #33

Earlier quoted context omitted.

"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 ca…

Blink (the HTML engine) is still going to push the same drawing commands to all the backends. Winding rule order stuff might be different if a backend is buggy, but things like this shouldn't be different.

"shouldn't", but historically I've observed that different backends have different behavior for filtering (of bitmaps and layers) and for text rasterization. Wouldn't be surprised if geometry rasterization could be different too.

Re: A div that looks different in every browser

#118

Post by lisper »

b2ccb2 wrote: post #95
lisper wrote: post #71

Earlier quoted context omitted.

Your code breaks the tag: if you try to nest a inside your it doesn't work. And my complaint is that I believe that computing should be accessible to everyone, and that simple things should not be made difficult just so that an elite guild can command above-market wages to fix problems that they themselves created. I don't believe in broken-windows economics.

Fixed: https://codepen.io/anon/pen/ZjzWzQ

Cool, thanks!

Re: A div that looks different in every browser

#119

Post by lisper »

talmand wrote: post #116
lisper wrote: post #71

Earlier quoted context omitted.

Your code breaks the tag: if you try to nest a inside your it doesn't work. And my complaint is that I believe that computing should be accessible to everyone, and that simple things should not be made difficult just so that an elite guild can command above-market wages to fix problems that they themselves created. I don't believe in broken-windows economics.

Wait, front-end developers who use CSS created the problems of CSS? That's really funny. I mean, that's the most mind-blowing accusation I've heard in a long time. I would have to suggest you are commenting on a topic that you actually know very little about. But at least you are entertaining.

Who do you think created CSS? CSS was not handed down on stone tablets by the gods, it was designed by humans, and I presume that at least some of the people who designed CSS actually used it (though to be honest I don't actually know who was on the committee). I don't know if it was their intent to make something Byzantine that served as an effective barrier to entry to doing front-end design, but that was in fact what they did.

Re: A div that looks different in every browser

#120

Post by pjmlp »

jhomedall wrote: post #113
pjmlp wrote: post #86

Earlier quoted context omitted.

Yeah and then they all jump around React as some amazing achievement, having rediscovereed how 90's native UI do event handling.

React isn't really anything like 90s UI libraries. It is, however, very much like the fairly recent native immediate-mode GUIs that have come out ( https://github.com/ocornut/imgui , https://github.com/PistonDevelopers/conrod , etc). The core feature of React is that your UI is a pure function of your application state. In (e.g.) the Win32 UI, you would receive events, and then need to manually transition your curren…

Smalltalk UIs used a pattern called dependency propagation to make objects update themselves based on system wide notifications.

Similar idea was used on Oberon System 3 Gadgets toolkit.

Also java.util.Observable based on the same Smalltalk ideas was already part of Java 1.0.

Post reply on HN