242546 - nsIContentUtils to centralize common code

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Aaron Leventhal]

We have a lot of code spread around that sits in various methods, taking up a
dozen lines to do very common things.

For example, code to check to see if a given content node is linked exists in
accessibility, find as you type, the code for scrolling by a page when space is
pressed, and the focus code (that's the original reason this was spun off from
bug 214843).

Jst wrote: 
> Aaron, I agree that it's lame to spread this code around, and I would love to
> put it in a centralized place, but a method like that does IMO not belong in
> nsIContent. If we'd have a singleton nsIContentUtils or somesuch, that would 
> be where this should go, but we don't yet, so there's no place yet to put a 
> helper like this.

Let's start a list of other very common things that nsIContentUtils could do, to
help make code more readable. If it makes sense we can implement it.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Please don't assign bugs to me unless I've explicitly asked for them.

Comment 2

[Aaron Leventhal]

In XHTML 2.0, anything can be a link by just having an href attribute.

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420