This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25164 - It's not clear what should be considered an object for the purpose of returning a property
Summary: It's not clear what should be considered an object for the purpose of returni...
Status: RESOLVED FIXED
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2014-03-26 21:29 UTC by Andrey Botalov
Modified: 2015-10-26 02:11 UTC (History)
2 users (show)

See Also:

Attachments

Description Andrey Botalov 2014-03-26 21:29:33 UTC 

    


    


      



        
          Comment 1
        

        
          Andrey Botalov

        

        
        

        
          2014-03-26 21:34:40 UTC
        

      






Step 7 of section 10.3.1 says:
"If this is defined and is not an object, then the named property of the object coerced to a string must be returned."

But AFAIK all (at least most of) types like DOMString map to objects. For example DOMString maps to String and String seems to be an object.

So it's not clear which types of properties should be transformed to strings and which should not.

    


    


      



        
          Comment 2
        

        
          David Burns :automatedtester

        

        
        

        
          2015-10-26 02:11:54 UTC
        

      






this has been corrected