-
cuki
Hello everyone, I have a question regarding the WebDriver standard there are 2 links, but what is the difference between
w3c.github.io/webdriver (living document) and
w3.org/TR/webdriver1 (CR level 1), is "Living Document" equal to "Working Draft"?
-
ato
cuki: No.
-
ato
cuki: The latter link is a snapshot taken 5 June 2018 when WebDriver went through the Recommendation track at W3C.
-
ato
cuki: The first link is a living document and reflects the tip of the git repo.
-
ato
cuki: Typically you will never use
w3.org/TR/webdriver1 for anything but give it to lawyers.
-
ato
cuki: The living document, on the other hand, represents the current reality as implemented by browser vendors.
-
cuki
ato: Thanks for that described explanation! In case I want to reference to the WebDriver standard, best would be then to use the living document, as it contains the latest changes which is most likely (to be) implemented by browser vendors, correct?
-
ato
cuki: Absolutely!
-
cuki
ato: Great, thanks for clearing that up!
-
ato
The changes in the living document are actually guaranteed to be implemented by at least two or more vendors.
-
ato
We don’t allow changes to the specification without commitment from vendors to implement them, or without tests.
-
ato
You might find
wpt.fyi/results/webdriver/tests?label=stable&aligned useful for tracking which drivers implement what.
-
ato
Of course there are bugs and so on, but generally what I said is true (-:
-
ato
Actually we should probably link that in the READMe.
-
cuki
Wow, that is a nice approach to "approve" changes, there is already a markdown in the repository about vendor status:
github.com/w3c/webdriver/blob/master/implementation-report.md
-
cuki
Edge is pretty far behind, looking at the tests :D
-
ato
Yeah, but unfortunately that refers to the level 1 spec.
-
ato
We should clarify that too…
-
ato
I don’t know, but Edge will probably abandon their implementation seeing as they’re switching to Chromium.
-
ato
)-:
-
cuki
What about reporting issues for Safaridriver? Where can I do this, for Geckodriver and Chromedriver there are some public repositories to report issues to.
-
cuki
For example if I look at
wpt.fyi/results/webdriver/tests/set_window_rect?label=stable&aligned, it shows that Safari properly supports /window/rect (POST) entrypoint
-
ato
-
ato
Or ping brrian in this room.
-
cuki
when in fact when specifying "0" or "1" as position value, it reads it as Boolean instead of Number, resulting in error: "Parameter 'x' has a boolean value, which is not allowed."
-
ato
Oh that sounds like a bug.
-
cuki
also from what I can deduct from the standard, it should also be possible to specify negative values for x/y when setting window/rect, no?
-
ato
Yes.
-
ato
Depending on the window manager and system, you may or may not see the window be moved off screen.
-
ato
But it will try its best.
-
cuki
Ok, for those cases I got a "no such window"
-
ato
-
cuki
aha, but the window is open, anyway, just checking, as you mentioned there are some bugs, but at least this is moving into a unified direction, which is awesome
-
cuki
Will check out
developer.apple.com/bug-reporting, as I have a few Safaridriver bugs to report
-
cuki
the weirdest one was that it could not send commands to a session browser instance when external monitors have the same name/specs
-
ato
I’m sure brrian would be interested to hear about that.
-
cuki
lost a good 3-4 hours pinpointing that issue :D
-
cuki
will have to verify once more before reporting, but have the monitors at the office
-
cuki
All right, thanks ato for taking the time to help and clarify with any questions I had, will see later if I can find anywhere to report Safaridriver bugs, as the link to developer.apple.com seems to be for development issues, not actual product issues.
-
ato
I have used it to successfully report bugs with Mail.app in the past.
-
ato
But I don’t think I’ve used it for safaridriver.
-
ato
Maybe you will find it listed under the product ‘Safari’.
-
cuki
ato: When you reported a bug, were you able to track it's progress or was it send into oblivion leaving you to hope and wonder?
-
ato
I… can’t remember.
-
cuki
Ah well, for now I've described the /window/rect issue with Safaridriver partially in this issue
webdriverio/webdriverio #3216 (under "Further comments") so brrian has something to read until I'll look into how to report a bug again tomorrow when I have both (identical) external displays to my disposal again.
-
gitbot
[webdriver] andreastt opened pull request #1386: Add testing documentation to README (master...wptfyi-link)
w3c/webdriver #1386
-
gitbot
[webdriver] andreastt closed pull request #1384: Fix inconsistency in key code table (master...key-code)
w3c/webdriver #1384