287
edits
XUL:Priority List: Difference between revisions
Jump to navigation
Jump to search
→Priority 2
| Line 37: | Line 37: | ||
==Priority 2== | ==Priority 2== | ||
#currently when one wants to filter out results that don't match a condition, an empty rule has to be used. There should be a simple way to negate results. | #<strike>currently when one wants to filter out results that don't match a condition, an empty rule has to be used. There should be a simple way to negate results.</strike> | ||
#need more control over template recursion. | #need more control over template recursion. Recursion can now be disabled. | ||
#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. | #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. | ||
#get the element at a given coordinate, or set of elements. | #get the element at a given coordinate, or set of elements. | ||