A div that looks different in every browser

Re:A div that looks different in every browser by chiefalchemist on Sunday July 08, 2018 @04:58PM (#17486156)

Yes. But are you going to to use 3 to 5 or mote C++ compilers on a given project?

The worst part of these frontend issues is, ultimately, the UX can become inconsistent, if not mess. Given that nearly everyone interfaces via the visual UI, you'd think we'd have this sorted out by now.

[ Parent | on HN ]

Re:A div that looks different in every browser by ben0x539 on Sunday July 08, 2018 @05:33PM (#17486327)

If your project is a library, I'd expect that people are gonna use it with, like, maybe not 5 but probably 2 or 3 different compilers, and they're gonna be less diligent about upgrading their compiler versions than mainstream browser users.

[ Parent | on HN ]

Re:A div that looks different in every browser by chiefalchemist on Monday July 09, 2018 @07:17AM (#17489405)

Thanks. I wasn't thinking about it that way. Good point.

That said, the browser's impact on UX is essential. A lot more people use browsers than compilers. You'd think the UX would matter by now.

[ Parent | on HN ]

Re:A div that looks different in every browser by ravenstine on Sunday July 08, 2018 @09:07PM (#17487265)

Does a single compiler work exactly the same on every architecture? :D

[ Parent | on HN ]