Closed Bug 825961 Opened 12 years ago Closed 9 years ago

see if we can remove the need for wrappedJSObject

Categories

(Remote Protocol :: Marionette, defect, P1)

Product:
Remote Protocol
Component:
Marionette
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1123506

People

(Reporter: mdas, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: pi-marionette-server, Whiteboard: [marionette=1.0])

Having to use wrappedJSObject interferes with WebDriver parity, since it's Gecko specific and we should just have access to the window object. Also, as more people start to use marionette, I figure this'll be a painpoint for them to remember, too. Perhaps we can use XPCNativeWrapper.unwrap(window) or the like.
OS: Mac OS X → All
(In reply to Malini Das [:mdas] from comment #0) > Perhaps we can use XPCNativeWrapper.unwrap(window) or the like. This is considered to be safe compared to wrappedJSObject(). I have mentioned that already in another bug but most likely never filed it.
WebDriver uses the older ways due to having to support so many older versions of Firefox. As long as the effect of using the API is the same we should be using more firefox idiomatic approaches.
Whiteboard: [webdriver-compat]
!! YAY
Blocks: webdriver
Whiteboard: [webdriver-compat] → [marionette=1.0]
Priority: -- → P1
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.