Bug 15159 – Links in WYSIWYG contentEditable mode are clickable.

• Status: RESOLVED
• Resolution: FIXED
• Component: HTML Editing

[Vincent Lee]

Steps to reproduce bug:

1. Turn a document into edit/WYSIWYG mode using: document.body.contentEditable = true;

2. Click on a link to edit the text in it.

Actual Result:
The link activates loading the linked page.

Expected Result:
The link should NOT activate, but be editable without moving to a new page. Once the link is no longer editable it may then be clicked activated by clicking on it or pressing ENTER with the link focused.

[Vincent Lee]

Created attachment 16224 [details]
Please use this HTML file to reproduce the issue.

When this page is first loaded, it is already editable. Selecting/Unselecting the checkbox can make the page editable/uneditable later on.

[Vincent Lee]

This issue is Mac only, tested with nightly build 25410. Works fine on Windows.

[Matt Lilek]

What version of Safari are you testing with?  This is a known issue with Safari 2 and works correctly with Safari 3 - <http://trac.webkit.org/projects/webkit/wiki/Known%20incompatibilities%20between%20open-source%20WebKit%20and%20Safari>.

[Vincent Lee]

I'm using the latest Mac OS X WebKit nightly build r25410 from: r25410.dmg">http://nightly.webkit.org/files/mac/WebKit-SVN-r25410.dmg .

[Matt Lilek]

(In reply to comment #4)
> I'm using the latest Mac OS X WebKit nightly build r25410 from:
> r25410.dmg">http://nightly.webkit.org/files/mac/WebKit-SVN-r25410.dmg .
> 

Yes, but what version of Safari (Safari -> About Safari)?  That disk image simply contains updated WebKit frameworks and does not alter the Safari browser at all (other than telling it to use those newer frameworks).

Are you using the standard version included in OS X 10.4.10 (Safari 2.0.4) or have you installed Safari 3 Public Beta.  If it's the former, this bug is invalid, and I'm thinking it is as I'm using Safari 3.0.3 Public Beta and your testcase behaves properly for me.

[Vincent Lee]

Thanks for pointing that out, and yes I'm using Safari 2.0.4. I'll check this again with Safari 3.

[Vincent Lee]

Yes, it works fine with Safari 3. Please close the bug, thanks.