> Therefore "ideal" WYSIWYG editing of HTML/CSS is not achieavable in principle.
I think users just need to be (made) aware that any & all web pages' design is always "template/theme"-driven. Even in the absence of CSS: the browser then falls back on its unique user stylesheets / factory defaults (black Times in unpredictable font-size on white background, unless maybe hi-contrast accessibility setup has the colors reversed, unless, unless, etc..)
MS Word-style "WYSIWYG" looks like a "simpler" problem in this respect because a piece of paper is a piece of paper (not really though as printing settings can easily mess with what what-they-saw-they-thought-they'd-get). Any sane web-page WYSIWYG must separate the content-formatting-without-tags (bold/italic/a picture floating to the right/etc) from style editing --- so will be essentially (at least) really "2 editors" (in 1).
Now as the user quickly grasps this intuitively after just a bit of tinkering, I don't really see the issue anymore?
> Therefore "ideal" WYSIWYG editing of HTML/CSS is not achieavable in principle.
I think users just need to be (made) aware that any & all web pages' design is always "template/theme"-driven. Even in the absence of CSS: the browser then falls back on its unique user stylesheets / factory defaults (black Times in unpredictable font-size on white background, unless maybe hi-contrast accessibility setup has the colors reversed, unless, unless, etc..)
MS Word-style "WYSIWYG" looks like a "simpler" problem in this respect because a piece of paper is a piece of paper (not really though as printing settings can easily mess with what what-they-saw-they-thought-they'd-get). Any sane web-page WYSIWYG must separate the content-formatting-without-tags (bold/italic/a picture floating to the right/etc) from style editing --- so will be essentially (at least) really "2 editors" (in 1).
Now as the user quickly grasps this intuitively after just a bit of tinkering, I don't really see the issue anymore?