#11158 closed defect (bug) (invalid)
Cannot Link Phrases With @ In Them (IE Only)
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.8.4 |
Component: | TinyMCE | Keywords: | needs-patch |
Focuses: | Cc: |
Description
Steps to Reproduce:
- Type a phrase into a new post body, such as "Old MacDonald @ The Farm"
- Highlight the phrase.
- Click the Link button.
- Type in any innocuous URL such as http://www.google.com/
Expected result:
Phrase should become linked. :)
Actual result:
Phrase is replaced by URL. :(
Workaround:
User must switch to HTML view and enter the link code manually.
Change History (13)
#4
follow-up:
↓ 5
@
15 years ago
- Summary changed from Cannot Link Phrases With @ In Them to Cannot Link Phrases With @ In Them (IE Only)
Fair enough.
#5
in reply to:
↑ 4
@
15 years ago
Replying to miqrogroove:
Fair enough.
Which version of IE are you seeing the issue in (and on what operating system)
This information will help us chase down this issue.
#7
@
15 years ago
Also broken in http://tinymce.moxiecode.com/examples/full.php
#8
@
15 years ago
- Resolution set to invalid
- Status changed from reopened to closed
Works for me under IE8 on that linked site.
Closing as invalid due to this NOT being a WordPress bug, Please report it to the Tiny MCE Bug tracker on Sourceforce
It seems to work for most(based on info here) so its probably an edge case with your setup which TinyMCE developers would know more info about.
#10
@
15 years ago
Once again, thanks for nothing.
What do you expect? Its NOT a bug in WordPress? If you can reproduce it on a non-wordpress site, it points the fact that its a problem in TinyMCE itself, and not the integration with WordPress. We're WordPress developers, NOT TinyMCE Developers, whilst some know enough to diagnose basic issues, Complex issues such as yours requires someone with itnernal knowledge of the product, You'll only find those on the proper channels for getting TinyMCE bugs fixed.
Seems to work properly in trunk. Was probably fixed in the newer version of TinyMCE.