W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2013

[Bug 20654] New: Have Range.surroundContents() work for partially contained nodes?

From: <bugzilla@jessica.w3.org>
Date: Sat, 12 Jan 2013 09:57:52 +0000
To: www-dom@w3.org
Message-ID: <bug-20654-4009@http.www.w3.org/Bugs/Public/>

            Bug ID: 20654
           Summary: Have Range.surroundContents() work for partially
                    contained nodes?
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
          Assignee: annevk@annevk.nl
          Reporter: annevk@annevk.nl
        QA Contact: public-webapps-bugzilla@w3.org
                CC: ayg@aryeh.name, mike@w3.org, www-dom@w3.org

"Why does Range#surroundContents() throw if you split a non-text node? The
logic is already there for extractContents(), so why not use it?"

"It’s trivial to work around, but means that surroundContents() isn’t very
useful as currently specced."

The reason the specification suggests it is done (in a comment in the source)
because it might be unexpected to clone containers.

Should we change this?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 12 January 2013 09:57:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:20 UTC