Context Navigation

Changes between Initial Version and Version 1 of Ticket #9998, comment 32

initial	v1
1		Most likely it was ~~intended~~ to be a feature, but it is very unwelcome feature. Webkit is just trying to do too much - it may look well (although I'm not sure about that), but the markup is corrupted. In the [http://code.google.com/p/chromium/issues/detail?id=226941 Blink/Webkit bug report] I described other behaviours which seem to be related - all them pay too much attention to visual aspect of editing, but not to markup and API, so the result is ridiculous.
	1	Most likely it was meant to be a feature, but it is very unwelcome feature. Webkit is just trying to do too much - it may look well (although I'm not sure about that), but the markup is corrupted. In the [http://code.google.com/p/chromium/issues/detail?id=226941 Blink/Webkit bug report] I described other behaviours which seem to be related - all them pay too much attention to visual aspect of editing, but not to markup and API, so the result is ridiculous.
2	2
3	3	And yes, removing all styles from contents.css will help for some of these issues in framed editor. You may check the file attached to bug report - I also needed to apply some styling to trigger these "features". However, this is not going to help in inline editing, where it's normal that many styles are applied to the content and it does not prevent from element transformation.