New issue
Advanced search Search tips
Starred by 24 users

Issue metadata

Status: Available
Owner: ----

Blocked on:
issue 1897
issue 1997
issue 2371

issue 2719

Show other hotlists

Hotlists containing this issue:

Sign in to add a comment

Issue 2536: Make standards mode (goog:chromeOptions.w3c:true) the default

Reported by, Aug 9 Project Member

Issue description

chromedriver should follow by default, as opposed to requiring opt-in to the standards compliant mode.

I propose changing the default value of the existing flag from false to true, so that people will need to opt in to the old behavior instead.

Comment 1 by, Aug 9

Blockedon: 1997

Comment 2 by, Aug 9

Project Member
Labels: StandardsCompliance Pri-2
Status: Available (was: Unconfirmed)
There are still many issues in how well ChromeDriver conforms to the standards (see all issues with label:StandardsCompliance). We can't flip the default until most of those issues are resolved. Flipping the default now would break the majority of applications that use ChromeDriver.

We will change the default mode to w3c when we are ready.

Comment 3 by, Aug 9

johnchen@, should this be blocked on all of, or is there some subset of those issues that matter most? For example, endpoints that are missing completely like in  issue 1936  seem like they ought not block, right?

Comment 4 by, Aug 9

Project Member
We haven't yet gone through all StandardsCompliance bugs to see which ones would block this one, and which ones don't. We also need to verify the completeness of the bugs, i.e., if there are any standards compliance issues that are not yet covered by any bugs.

Comment 5 by, Aug 17

Blockedon: 2371

Comment 6 by, Aug 17

Blockedon: 1897

Comment 7 by, Aug 21 is a good guide for what should potentially be linked to this issue. Not every issue is serious though, so I won't mark them all as blocking.

Comment 8 by, Dec 28

Project Member
Blocking: 2719

Comment 9 by, Jan 8

Project Member
 Issue 2725  has been merged into this issue.

Sign in to add a comment