8 ms·
You are assuming that your developers were perfect and write sites exactly to the standard every time. In the real world they don't and XHTML lost, so all brows
by pavon 3y ago
You are assuming that your developers were perfect and write sites exactly to the standard every time. In the real world they don't and XHTML lost, so all browsers tolerate and mask non-compliant pages to various degrees and in various ways, and will surface different bugs in your work. So it behooves you to test with the browsers your users are using to find those bugs before they do.
- ndriscoll 3y agoI am assuming that a professional can do their job, yes. The whole XHTML thing where allegedly it never caught on because people can't write valid markup has never made sense to me. They're able to get typescript to compile now, right? If a dev couldn't write react code that compiles, we would fire them, right? We have tools to check that your document parses and conforms a schema. We've had them for 20 years. It's easy enough to have that be part of your CI pipeline. The tooling is 1000x simpler than modern frameworks, and the thing that was allegedly difficult was that if you enabled conformance mode (which was opt-in based on DTD and/or MIME type), you had to open and close your tags instead of just opening them. Surely any middle schooler understands when you open a parenthesis, you need to close it?
- deleted 3y ago[deleted]