Closed
Bug 193073
Opened 22 years ago
Closed 19 years ago
Type-ahead should be able to override "onfocus="blur()" for links
Categories
(SeaMonkey :: Find In Page, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: thos, Assigned: aaronlev)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 The site has links of type <script language="javascript"> G34(514368,'','Det kniber med det rene vand'); </script> invoking the following function: <script Language="Javascript">function G34(PID, trumpet, rubrik) { document.write(trumpet+' <a href="/VisArtikel.iasp?PageID='+(PID-1946)/2+'" class=noline onfocus="this.blur()">' + rubrik + '</a>'); } </SCRIPT> Typeahead find the links as usual, but it is not possible to activate them by pressing enter. The links work fine if you click them with the mouse. Reproducible: Always Steps to Reproduce: 1. Use typeahead to find links on page 2. Press enter Actual Results: nothing happens Expected Results: Typeahead should follow the links, since mozilla has no problem recognizing them as such.
Comment 1•22 years ago
|
||
> onfocus="this.blur()"
This means you can't even focus the link to hit enter on it. Which seems to be
a conscious decision on the part of the site to lock out keyboard users from
using that link (the wisdom of this decision is questionable).
Reporter | ||
Comment 2•22 years ago
|
||
Ok, comment #1 is correct, I should have checked if ordinary keyboard navigation was possible on the site. However, since it would be extra nice if type-ahead worked with these kind of pages, I'm changing the bug to a enhancement request, that type-ahead should be able to override "blur()" for links. I am not capable of judging whether this is technically possible.
Severity: normal → enhancement
Summary: Type-ahead cannot activate links invoked by javascript function → Type-ahead should be able to override "onfocus="blur()" for links
Comment 3•19 years ago
|
||
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/
Comment 4•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•