User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803 Whether or not Midas displays the contents of <a>...</a> as a link (i.e. blue text with underline) seems to depend on the URL used in the href. Specifically, if the URL contains a colon, it is displayed as a link. If the URL does not contain a colon it is not displayed like a link. For example: <a href=":">this looks like a link</a> but <a href="/">this does not look like a link</a> Reproducible: Always Steps to Reproduce: 1.Go to http://www.mozilla.org/editor/midasdemo/ and enter some text. 2.Highlight a word and click the "Insert Link" icon 3.When prompted for the URL enter "/" Actual Results: Linked text does not look like a link (just plain black text). Expected Results: Should look like a link (blue text with underline)
hm... base uri is about:blank... about: does not support relative uris... / would be a relative uri.. so mozilla can't create a uri object, and <a> w/o uri objects are not rendered as links
While trying to figure out another problem (broken images with relative URLs - see bug 192945) I finally figured out what Christian is talking about in comment 1. The iframe that was used to hold the editor did not have a "src" value, so relative URLs cannot be understood by the browser. A really kludgy fix is to do something like: <iframe src='/nosuchfile' ...> for the iframe that holds the editor. A "file not found" error will display briefly before the text to be edited replaces it, but relative links will display correctly. Is there a better fix?
xref bug 166644