Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stacktrace -> stackTrace #1006

Closed
barancev opened this issue Aug 14, 2017 · 2 comments
Closed

stacktrace -> stackTrace #1006

barancev opened this issue Aug 14, 2017 · 2 comments

Comments

@barancev
Copy link

https://w3c.github.io/webdriver/webdriver-spec.html#processing-model

In SeleniumHQ/selenium#3683 @AutomatedTester wrote:

"We're going to have to update the spec to do stackTrace."

@andreastt
Copy link
Member

If the clients are changing anyway to look for stacktrace, why can’t this be a permanent change? I’m skeptical of making API breaking changes at this point because it hits Mozilla, as the first spec conforming implementor, quite hard.

@shs96c
Copy link
Contributor

shs96c commented Aug 15, 2017

stacktrace is defined in the spec as an implementation-defined string containing a stack trace report of the active stack frames at the time when the error occurred.

stackTrace from the JSON Wire Protocol is a structured type, composed of a list of objects.

Making the spec use stackTrace will cause unexpected bugs with older selenium clients. I strongly suggest not making the spec change the casing of "stack trace"

@shs96c shs96c closed this as completed Aug 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants