search

webcompat / webcompat.com

Source code for webcompat.com
https://webcompat.com
357 stars 191 forks source link

Webcompat.com in devtools #1985

Open adamopenweb opened 6 years ago

adamopenweb commented 6 years ago

Some comments came out in a non-webcompat meeting at Austin all hands about capturing bug information from devs in developer tools. The desire is to encourage devs to report issues to us while building / testing and webcompat.com has a good process.

Currently we don't capture a screenshot of dev tools from a reporter. This works for most users, but maybe we should consider the option to allow developers to report compat issues from dev tools.

We could capture a screenshot of the devtools, save a copy of the code and even make the issue private (send the bug to a private repo on GH).

This isn't a priority, but I wanted to document for discussion.

miketaylr commented 6 years ago

It sounds like an interesting idea for sure.

karlcow commented 6 years ago

Interesting idea. I wonder what kind of information the developer would be willing/interested to share. When doing diagnosis, for example, it's common I will show the events on a node or a piece of markup.

There are interesting features in devtools, such as screenshot this node (in inspector). I wonder if we could start with a small proof of concept, something very manageable, such as send a screenshot of this node to webcompat.com for example.

Also would developers be interested by this feature and how is maybe the first question we need to resolve.

zoepage commented 6 years ago

I agree. It would be a really cool feature.

Which information should we collect? Just the log or also information like e.g. which framework is used?

@karlcow

Also would developers be interested by this feature and how is maybe the first question we need to resolve.

What do you mean by this? Compatibility information for the developer?

karlcow commented 6 years ago

What do you mean by this? Compatibility information for the developer?

@zoepage I meant that the first step is asking to real web developers (and not Mozilla people), if they would be interested by a tool.

@adamopenweb said (emphasis mine):

Currently we don't capture a screenshot of dev tools from a reporter. This works for most users, but maybe we should consider the option to allow developers to report compat issues from dev tools.

Before developing anything or even starting a list of features, we need to ask web developers if it is something they need and if yes, how they would see it.

Let's not put the cart before the horse 🐴

zoepage commented 6 years ago

@karlcow

Currently we don't capture a screenshot of dev tools from a reporter. This works for most users, but maybe we should consider the option to allow developers to report compat issues from dev tools.

Before developing anything or even starting a list of features, we need to ask web developers if it is something they need and if yes, how they would see it.

As far as I understand this, the idea is to collect some data from e.g. the console and attach this to the report. Right? I think, this is a great idea and should be manageable to collect. Before doing that, we would need to know which information is useful for the report or which features it would require to be useful.

What do you mean by this? Compatibility information for the developer?

I meant that the first step is asking to real web developers (and not Mozilla people), if they would be interested by a tool.

This is always a good idea, but this is not answering my question. :) In this context I understand "developer" as someone, who is not diagnosing bugs, but developing sites. Why would they need this feature?

karlcow commented 6 years ago

(trying to give more context/ edited) Maybe it would be better if @adamopenweb explained a bit more the original issue so it clears up a bit the confusion we have. Maybe it will help to draw a better understanding.

@zoepage I have just copied what @adamopenweb wrote:

we should consider the option to allow developers to report compat issues from dev tools.

What I read from @adamopenweb:

  1. Web developers take an action to report a bug inside the context of devtools UI.
  2. "capture a screenshot of the devtools" (I don't know what it means)
  3. "save a copy of the code" (unclear what it means given how complicated a Web page is.)

so before working on 2 and 3, the 1 should be clarified. Do developers want that? And if yes, what would be practical for developers.