Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Exploration of metadata on webcompat.

A current report on webcompat.com

<!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->

**URL**: https://www.reddit.com/r/RetroPie/comments/cjcrnk/pi4_overclock_vs_stock_dreamcast/

**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: No 

**Problem type**: Site is not usable
**Description**: Cant scroll
**Steps to Reproduce**:
Cant scroll in mobil mode, only in desktop
[Screenshot](https://webcompat.com/uploads/2020/1/a9c265e6-e275-45ad-85a7-980add5d34a8.jpeg)

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191207035001</li><li>channel: default</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2020/1/05ebd3d2-e98c-4dfb-97fa-b46359c2bb92)

_From [webcompat.com](https://webcompat.com/) with ❤️_

In the case of a anonymous report it would be on the private-repo:

<!-- @browser: Firefox Mobile 68.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/47690 -->

**URL**: https://www.reddit.com/r/RetroPie/comments/cjcrnk/pi4_overclock_vs_stock_dreamcast/

**Browser / Version**: Firefox Mobile 68.0
**Operating System**: Android
**Tested Another Browser**: No 

**Problem type**: Site is not usable
**Description**: Cant scroll
**Steps to Reproduce**:
Cant scroll in mobil mode, only in desktop
[Screenshot](https://webcompat.com/uploads/2020/1/a9c265e6-e275-45ad-85a7-980add5d34a8.jpeg)

<details>
<summary>Browser Configuration</summary>
<ul>
  <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191207035001</li><li>channel: default</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>

[View console log messages](https://webcompat.com/console_logs/2020/1/05ebd3d2-e98c-4dfb-97fa-b46359c2bb92)

_From [webcompat.com](https://webcompat.com/) with ❤️_

There are 5 sources of data

  • <!-- @key: value --> (metadata)
  • details with a list of configs
  • screenshot link
  • URL in text **URL**: http://example.com (here we should have probably recorded this as a meta too)
  • console log link

Maybe we could explore a solution based on json? Maybe we could just save all these meta into a DB or individual flatfiles or…

flat file is a simple accessible db

<!-- @meta: https://webcompat.com/meta/2020/01/issue-47690.json -->

so when there is an event the webhook look at the body, see this URI and go fetch it. with it, it starts to assign labels milestones, etc.

Benefits: easy local rsync to get the data on your machine for stats

commit files into a private repo

Let's say that instead of saving to a flat file. This is committing the json into a private repo. The private repo could be editable and modifiable easily. (checkout, fetch, commit, push) with an history on why and when we modified the metadata.

This could even trigger modifications on the visible issue. Same benefits than flat files for search/stats, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment