>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.
this is incorrect. almost every modern WYSIWYG editor includes support for media queries.
People 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.
Re:Google Web Designer (2013)
by FroshKiller on Friday December 16, 2016 @08:02AM
(#13192930)
But 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.
WYSIWYG requires a fixed layout size, which was common back when dreamweaver/frontpage were around.