If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Midas does not display <a> as a link for certain URLs




13 years ago
12 years ago


(Reporter: Bill Dimm, Assigned: Joe Francis)



Firefox Tracking Flags

(Not tracked)





13 years ago
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

Comment 2

13 years ago
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?

Comment 3

13 years ago
xref bug 166644
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.