282742 - Support nsIContent::IsContentOfType(nsIContent::eXTF)

Status: RESOLVED WONTFIX

(Core Graveyard :: XTF, defect)

Description

[Aaron Leventhal]

nsIContent::IsContentOfType(nsIContent::eXTF) would be useful, rather than
needing to use a QI to see if we're currently on an XTF element.

Comment 1

[Aaron Leventhal]

Attachment: Simple patch

Comment 2

[Boris Zbarsky [:bzbarsky]]

What does "XTF elements" mean?  It seems rather underdefined...  In particular,
why is this needed for nsXTFVisualWrapper, but not nsXTFElementWrapper?

Comment 3

[Aaron Leventhal]

Good question. I don't know enough about XTF to answer. Maybe we need it on the
other XTF elements, but I'm not sure what each class is used for. When is
nsXTFElementWrapper used?

Comment 4

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 174715 [details] [diff] [review]
Simple patch

Marking sr- pending better documentation of what this constant means, at least.

Comment 5

[Alex Fritze]

Comment on attachment 174715 [details] [diff] [review]
Simple patch

You should either set this for nsXTFElementWrapper (the common baseclass for
all XTF elements: visuals and "display=none"-like elements), or rename it to
something like eXTFVisual - depending on how and where you want to use this
flag.

Comment 6

[David Bolter [:davidb] (NeedInfo me for attention)]

Mass un-assigning bugs assigned to Aaron.

Comment 7

[Alex Vincent [:WeirdAl]]

XTFVisual is long gone... perhaps under the current code, this could only work for nsXTFElementWrapper.

Is this still wanted?  What clarifications still are needed?

Comment 8

[Alex Vincent [:WeirdAl]]

XTF has been removed from the tree.  [xtfisdead] for filtering purposes.