W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2012

[Bug 20171] New: There is no clear statement when APIs for the text field selections can be applied

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 Nov 2012 12:11:51 +0000
To: www-dom@w3.org
Message-ID: <bug-20171-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20171

            Bug ID: 20171
           Summary: There is no clear statement when APIs for the text
                    field selections can be applied
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: major
          Priority: P2
         Component: DOM
          Assignee: annevk@annevk.nl
          Reporter: termi1uc1@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

Created attachment 1251
  --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1251&action=edit
Different behavour between {FireFox, Opera} and Chrome

Spec say: "For input elements, calling these methods while they don't apply,
and getting or setting these attributes while they don't apply, must throw an
InvalidStateError exception."
No browser has implemented InvalidStateError error. And the is no clear
statement, that does "while they don't apply" mean.

Can we call element.setSelectionRange while element has no focus?

The are two different model in browsers I tested:

1. FireFox and Opera, set selectionStart and selectionStart values without
setting focus.
2. Chrome, set selectionStart and selectionStart values with setting focus to
current element.

Both behavior seams wrong. But Chrome behavior is worse, due it broke events
queue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 30 November 2012 12:11:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 30 November 2012 12:11:58 GMT