Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327992

Summary: [Browser-Safari] Links in HTML editors react to clicks
Product: [Eclipse Project] Platform Reporter: Christopher Deckers <chrriis>
Component: SWTAssignee: Grant Gayed <grant_gayed>
Status: NEW --- QA Contact: Scott Kovatch <skovatch>
Severity: major    
Priority: P3 CC: skovatch
Version: 4.0   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X   
Whiteboard:
Attachments:
Description Flags
Browser loading the TinyMCE editor, with a window listener to see the error none

Description Christopher Deckers CLA 2010-10-17 12:38:48 EDT 
Build Identifier: SWT N20101016-2000

When an HTML editor (TinyMCE or other) shows a link, SWT Safari integration handles it as a real link: mouse changes when hovering it, clicking it opens the page.
Opening the same editor directly in Safari behaves as expected: hovering the link shows a caret, clicking has no effect.

This is major because a user actually clicking on the link loses all its changes if the link has a property of opening in the parent window. Moreover I know many people integrating TinyMCE who are actually affected.

Reproducible: Always

Steps to Reproduce:
1. Create a Browser using Safari (default on Mac)
2. Navigate to http://tinymce.moxiecode.com/examples/full.php
3. Click on a link in the editor
Comment 1 Christopher Deckers CLA 2010-10-17 12:40:16 EDT 
Created attachment 181050 [details]
Browser loading the TinyMCE editor, with a window listener to see the error
Comment 2 Scott Kovatch CLA 2010-10-18 12:11:28 EDT 
Starting with Grant, as this looks DOM-related.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:32:48 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.