287
edits
XUL:Priority List: Difference between revisions
Jump to navigation
Jump to search
→Priority 2
No edit summary |
|||
| Line 40: | Line 40: | ||
|there are various targets and elements available through an event object but it seems that none of them are ever the one I want. Often they point to anonymous content. (AxelHecht) more detail here? (NeilDeakin) For example, for focus events, the target is the anonymous HTML input rather than the XUL element. (NeilRashbrook) This is because the focus event doesn't bubble so the onfocus handler has to be inherited onto the anonymous HTML input.||XBL2|| | |there are various targets and elements available through an event object but it seems that none of them are ever the one I want. Often they point to anonymous content. (AxelHecht) more detail here? (NeilDeakin) For example, for focus events, the target is the anonymous HTML input rather than the XUL element. (NeilRashbrook) This is because the focus event doesn't bubble so the onfocus handler has to be inherited onto the anonymous HTML input.||XBL2|| | ||
|- | |- | ||
|get the element at a given coordinate, or set of elements.|| | |<strike>get the element at a given coordinate, or set of elements. Use elementFromPoint. </strike>|||| | ||
|- | |- | ||
|get XUL elements to work well in XML documents. (NeilRashbrook) Many of the XUL helper methods are currently defined on the XUL document. (AxelHecht) Is this part of my favorite content sink story or vice versa?|||| | |get XUL elements to work well in XML documents. (NeilRashbrook) Many of the XUL helper methods are currently defined on the XUL document. (AxelHecht) Is this part of my favorite content sink story or vice versa?|||| | ||