4 ms·
The biggest reason is that WYSIWYG doesn't really work on the web. What you see on your screen isn't what someone else will see because their monitor is a diffe
by flukus 10y ago
The biggest reason is that WYSIWYG doesn't really work on the web. What you see on your screen isn't what someone else will see because their monitor is a different size or they are on a mobile device.
WYSIWYG requires a fixed layout size, which was common back when dreamweaver/frontpage were around.
- tribby 10y agothis is incorrect. almost every modern WYSIWYG editor includes support for media queries.
- flukus 10y agoPeople that understand media queries don't need WYSIWYG editors. And there are still issues like css being polite suggestions rather than rules a browser has to follow. Firefox recently introduced a readability mode for instance.
- coldtea 10y ago>People that understand media queries don't need WYSIWYG editors. That's wrong, and analogous to saying that people who understand low level programming don't need IDEs.
- FroshKiller 10y agoBut CSS styling pretty much is a polite suggestion. The browser's job is to retrieve and display content according to the user's needs and preferences. If the designer and the user disagree about whether an unvisited link should be underlined and blue, the user wins. If the designer and the user disagree about whether a page should contain images, the user wins.
- coldtea 10y ago>The biggest reason is that WYSIWYG doesn't really work on the web. What you see on your screen isn't what someone else will see because their monitor is a different size or they are on a mobile device. Different screen sizes and WYSIWYG use are orthogonals. Any WYSIWYG editor worth its salt has supported media queries, previewing on different screen sizes, breakpoints, etc for ages.