andreastt
andreastt
Put into other words: This is output you’d see from Firefox normally, even when not run through geckodriver.
`browser.dom.window.dump.enabled` only controls the visibility of `dump()` in JS. It does not control `std::cout` or `printf` in C++ or C. For example, I still see this which originates from C++...
Sure. I’ve always found them useful, but I guess it would be more structured to access them by implementing a [log retrieval API](https://github.com/w3c/webdriver/issues/406) in the future. In the meantime, users...
> I assume you meant not interested because we enable this preference by default in geckodriver. I mean that when `browser.dom.window.dump.enabled` is taken out of prefs.rs, users who are interested...
The debug-level output you see from the Marionette component there is due to https://bugzilla.mozilla.org/show_bug.cgi?id=1384956.
This happens because the `` element isn’t scrolled into view first. Marionette finds the in-view centre coordinates of the targetted element in the framed document, but the click happens at...
@whimboo I don’t think it will be, and I suspect there is some specification work required here but this edge case will probably not be fixed by level 1 of...
I’ve filed https://github.com/w3c/webdriver/issues/1141 against the spec. I think we should fix the spec before addressing this.
Follow https://bugzilla.mozilla.org/show_bug.cgi?id=1314462 for progress.
@jgraham mentioned https://github.com/rust-lang/rfcs/issues/1368.