Opened 15 years ago

Closed 14 years ago

#456 closed defect (wontfix)

getElementsByClass fails on mozilla richedit content

Reported by: [email protected] Owned by: Bryan Forbes
Priority: high Milestone: 0.9
Component: Widgets Version: 0.2
Keywords: Cc:
Blocked By: Blocking:


getElementsByClass function seems to work fine on the html editor richtext part in ie, but fails miserably to deliver anything in content within the mozilla rich text editor.

a href within the rich text content with a class="myFaces_SpellingError". The href is shown and triggerf

now if I trigger following code: var errorHrefs = dojo.html.getElementsByClass("myfaces_SpellingError", document,"*",0); errorHrefs is an empty array while on the same content the whole thing is returned back as an array with all the hrefs set to class="myfaces_SpellingError"

I am not sure if this is fixable, a workaround is to set the code directly within the href which has to be triggered instead of pushing it in afterwards. via dom element alteration, so that getElementsByClass calling is not needed. As I said I am not sure if this is fixable, but definitely worth an investigation.

Change History (7)

comment:1 Changed 15 years ago by anonymous

Priority: highnormal
severity: normalmajor

comment:2 Changed 15 years ago by dylan

Milestone: 0.5

comment:3 Changed 15 years ago by dylan

Milestone: 0.50.4
Owner: changed from anonymous to Bryan Forbes

Bryan, is this still an issue after your html refactor?

comment:4 Changed 15 years ago by dylan

(In [6203]) references #456, references #959, temporary workaround until we figure out why the xpath version of getElementsByClass does not work 100% reliably in firefox

comment:5 Changed 15 years ago by dylan


comment:6 Changed 15 years ago by bill


comment:7 Changed 14 years ago by bill

Resolution: wontfix
Status: newclosed

Functionality replace by dojo.query()

Note: See TracTickets for help on using tickets.