The web is a really big place and your users are accessing your sites from all sorts of browsers and devices. What happens when things go wrong, and you can't reproduce them? This talk will show you how to do remote, client-side debugging on any browser and any device using Vorlon.js. We will also look at how it's implemented, and how you can extend it. The web should just work for anyone on any device. You'll leave this talk better equipped to make that happen.
Last active
November 7, 2015 01:04
-
-
Save jaredfaris/3a9da4945db053601010 to your computer and use it in GitHub Desktop.
A talk about remotely debugging web applications in any browser/platform with Vorlon.js
Jared...sounds interesting. Perhaps describing a little more around how "Remotely" plays in. I wonder if you are debugging a webserver from your device or are you debugging the instance of the website on your device. I assume the talk would cover this, but it might be useful to be more explicit. If not on your outline I would be interested in how security plays into this topic.
@RyannosaurusRex thanks
@CognitiveBurden - I'll think about how to be more explicit that this is actually accessing the client; the DOM, rendered styles, console, etc as is in the actual browser. Would using the term "client-side debugging" be clear enough?
@CognitiveBurden - How about the sentence "This talk will show you how to do remote, client-side debugging on any browser and any device using Vorlon.js"?
I'll definitely talk about security during the session (spoiler: nothing to worry about) but probably don't want to include it in the abstract.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10/10 would attend.