Confirmed users
269
edits
XUL:New Widgets: Difference between revisions
m
no edit summary
(html:a) |
mNo edit summary |
||
| Line 10: | Line 10: | ||
Answering NeilRashbrook's [[XUL:Priority_List#Priority_5|question]], <html:a> can't be used as is because: | Answering NeilRashbrook's [[XUL:Priority_List#Priority_5|question]], <html:a> can't be used as is because: | ||
* it isn't even visible when used used as <code><html:a href="about:">some text</html:a></code> | * it isn't even visible when used used as <code><html:a href="about:">some text</html:a></code> | ||
** (Neil) That's what you get for mixing box models. But you should be using <xul:label> or <xul:description>, not <html:p>. | |||
* not styled properly, if you get it to show by enclosing it in a <html:p> tags | * not styled properly, if you get it to show by enclosing it in a <html:p> tags | ||
* and opening the link in the same (often chrome) window when clicked. | * and opening the link in the same (often chrome) window when clicked. | ||
** (Neil) I suggested to bz that chrome URI content listeners should not offer to handle link clicks, although that's not possible the way URI content listeners currently work. | |||