Not all of the underlying code may be written for WYSIWYG. So, some views may not exist. There could be some command line prompts to older code or non-WYSIWYG functions.
Example: In Windows, click START > RUN and enter CMD. This will bring up a command line prompt within Windows to enable commands to be entered directly without the WYSIWYG GUI.
I suppose other reasons could be programming error, data corruption, unexpected exceptions and so forth.
2006-10-02 07:10:58
·
answer #1
·
answered by Plasmapuppy 7
·
0⤊
2⤋
Most wysiwyg editors display the page being built in a smaller area than the actual browser window to be used, this can lead to some strange effects especially when working with CSS formatted pages. Another issue is images, especially links to off site images which the editor can not resolve. Of course if you are using any sort of scripting to alter the page, the alterations will not show, instead showing a placeholder for the embedded code. As each browser uses its own uniquely coded rendering engine, often the actual results will be different than the pseudo rendering engine used in the editor.
2006-10-02 07:31:08
·
answer #2
·
answered by Interested Dude 7
·
0⤊
1⤋
I'm not sure if I understand your question correctly. If I do and you mean why do some editors have a non-wysiwyg component (i.e. Dreamweaver's code view) it is because there are some things you can't do in a wysiwyg editor. Many of the advanced features either can't or aren't supported in GUI mode. I haven't used Dreamweaver, or any other wysiwyg editor (I prefer to control it all manually), in a while, so I can't point to specific examples unfortunately.
2006-10-02 07:42:23
·
answer #3
·
answered by John J 6
·
1⤊
0⤋
One common problem is using fonts that aren't available on the target system.
WYSIWYG HTML editors frequently produce unexpected results because HTML was never intended for rigidly formatted output. Browsers can display elements in various ways, plus users can control fonts, font sizes, page sizes, and other aspects.
2006-10-02 07:43:43
·
answer #4
·
answered by injanier 7
·
0⤊
1⤋
Usually it is due to run-time errors or so called flow of logic. The computer cannot sense wether you're instructions are right or wrong but it can only check wether your syntaxes are correct.
What You See Is What You Get....
2006-10-02 07:12:45
·
answer #5
·
answered by JarmenKell 4
·
0⤊
2⤋
i take it you mean - WYSIWYG (what you see is what you get).
if the coding is corrupt, or has errors.
2006-10-02 07:11:48
·
answer #6
·
answered by UKDealsBox.com 4
·
0⤊
2⤋