Remove isElementContentWhitespace

RESOLVED FIXED in mozilla10

Status

()

defect
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: annevk, Assigned: Ms2ger)

Tracking

({addon-compat, dev-doc-complete})

Trunk
mozilla10
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Text.isElementContentWhitespace is no longer part of the DOM standard.
WebKit does not support this attribute. I filed a bug on Opera for removing it there (along with replaceWholeText()).
Posted patch Patch v1Splinter Review
Assignee: nobody → Ms2ger
Status: NEW → ASSIGNED
Attachment #560927 - Flags: review?(jonas)
Depends on: 688190
Keywords: dev-doc-needed
OS: Mac OS X → All
Hardware: x86 → All
Jonas?
Comment on attachment 560927 [details] [diff] [review]
Patch v1

Hrm.. this actually seemed like a useful function. It always feels silly to me when all browsers have to have state or functionality internally that isn't exposed to the webpage.

So I'd be in favor of keeping this in spec/implementations. But if people prefer to remove it then I won't stand in the way.
Attachment #560927 - Flags: review?(jonas) → review+
The current name does not make any sense. I would be open to renaming it. E.g. Text.isWhiteSpace. I used an uppercase S for consistency with white-space in CSS.
I filed http://www.w3.org/Bugs/Public/show_bug.cgi?id=14443 on adding Text.isWhiteSpace to DOM4, but Simon rightly asks what the use case is and I have no idea.
https://hg.mozilla.org/mozilla-central/rev/292803c8c406
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla10
Version: unspecified → Trunk
Keywords: addon-compat
Oops, wrong bug (sorry for the spam).
You need to log in before you can comment on or make changes to this bug.