Project:Whizzywig - A complete WYSIWYG Editor
Version:6.x-1.0-beta7
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active
Issue tags:disappears, link, text

Issue Summary

The link icon does not seem to work. I highlighted some text eg "bbc web" added the link and ticked open in a new window and then pressed ok. The text disappeared. When I looked at the html it had deleted the text

<div>go to the&nbsp;<a href="http://bbc.co.uk" target="_blank"></a>&nbsp;&nbsp;</div>

it DOES work ok if you dont tick the open in new window box

regards joe

Comments

#1

Hi,

Try 6.x-1.0-BETA6 and please reporting back the result.
I have test it and working fine.

Rgds

#2

Version:6.x-1.0-beta4» 6.x-1.0-beta7

tested with beta 7 - no better I am afraid

#3

Hi,

I can not produce this bug. Can you inform me what is the link that you have entered?
I need to reproduce this bug so I can confirm this as a bug, so we can deliver a bug fix.

#4

i have the same promlem with 6.x-1.0-beta8.

adding link of any kind with "new window" option is on, "eating" any text.

#5

I had this problem and it was fixed after I had done the following:

  • Uninstalled WYSIWYG module and folders.
  • Removed the /sites/all/libraries directory where whizzywig directory and whizzywig.js file had previously been when I was using Whizzywig standalone files with WYSIWYG module.
  • Flushed all Drupal caches and browser caches.
  • Customized some css in simple.css and whizzywig.js, but the css customizations had nothing to do with anchors or target attributes.

EDIT: I still have this issue in Safari 4.0.5. Selected text gets eaten and a mysterious and seemingly random &nbsp; is appended before the link code.

#6

Looks like it might be a Webkit-only issue. Tried this in Chrome with similar results, and as jrstmartin said, it is also happening in Safari. Had the user try in FF3 and everything works fine. Im using version 1.4.

#7

I can verify #6 dmlinn’s observation that it appears to be Webkit-specific.

That said, Webkit is the web layout engine that, of the top four widely available web layout engines, first passed Acid3 with flying, er, colors.

From their descriptive web site:

Acid3 is primarily testing specifications for “Web 2.0″ dynamic Web applications. Also there
are some visual rendering tests, including webfonts. Here is the list of specifications tested:

  • DOM2 Core
  • DOM2 Events
  • DOM2 HTML
  • DOM2 Range
  • DOM2 Style (getComputedStyle, …)
  • DOM2 Traversal (NodeIterator, TreeWalker)
  • DOM2 Views (defaultView)
  • ECMAScript
  • HTML4 (, , …)
  • HTTP (Content-Type, 404, …)
  • Media Queries
  • Selectors (:lang, :nth-child(), combinators, dynamic changes, …)
  • XHTML 1.0
  • CSS2 (@font-face)
  • CSS2.1 (‘inline-block’, ‘pre-wrap’, parsing…)
  • CSS3 Color (rgba(), hsla(), …)
  • CSS3 UI (‘cursor’)
  • data: URIs
  • SVG (SVG Animation, SVG Fonts, …)

Given this, it’s quite probable that whatever incompatibility is causing this is an incompatibility with current ECMAscript/DOM standards that, if not already present, will likely start showing up in other browser web layout engines as newer releases of their browsers are released (IE9, Firefox 4, Opera 11, etc.). It really needs to be fixed, and not just waved aside with an, “Oh, that’s just Webkit. Tell ’em to use another browser.”

Also, Google Chrome alone (not even counting Safari) is already nipping at Firefox’s heels in the race to be #2 to IE among actual browser usage (remember that it’s the default installed browser on all those Droid and Android smartphones and similar devices out there!). Some rankings show it as having already surpassed the mighty Firefox! It’s no longer safe to just discount it.

Note also that it isn’t just erasing the link text. It’s also inserting a non-breaking space (“&nbsp;”) both before the opening <a href=…> tag and after the closing </a> tag.