Bug 30152 (designMode) - Absolute positioned elements in designedMode are still in the DOM flow
Summary: Absolute positioned elements in designedMode are still in the DOM flow
Status: NEW
Alias: designMode
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords: NeedsReduction
Depends on:
Blocks:
 
Reported: 2009-10-06 23:09 PDT by jaroslav.benc
Modified: 2012-05-01 22:41 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jaroslav.benc 2009-10-06 23:09:08 PDT 
Not sure if this is a bug, but works well in Firefox - when there is an absolute positioned element in the document (designMode='on') this element is accessible via navigation keys moving caret. So let say we have this example from my online editor:

<div class="line-numbers-absolute"></div>
<span class="line-relative">some text line1</span>

in editor you can see this:
some text line1

so if the caret is in the beginning of the text and left arrow is pressed caret jumps somewhere into absolutely positioned div (line numbers). Firefox works well so I think they deal with key navigation according to the DOM flow. Seems like webkit deal with key navigation via HTML. 

I've found some JS workaround, but it's not very pretty and I think it'd be good to think about this so it's same in all browsers. 

Cheers, 
Jaro
Comment 1 Ryosuke Niwa 2012-05-01 22:41:01 PDT 
This is a pretty tricky bug to fix.