profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/dontcallmedom/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

darobin/webref 2

References for Web Specifications (http://webref.herokuapp.com/)

dontcallmedom/api-design-cookbook 2

A cookbook for Web API design

dontcallmedom/canon-singing 2

A node-based Web app to record and play a distributed canon song (Frère Jacques for now)

darobin/vision 1

Web Vision

dontcallmedom/adoption-monitor 1

https://dontcallmedom.github.io/adoption-monitor/

dontcallmedom/bikeshed 1

:bike: A preprocessor for anyone writing specifications that converts source files into actual specs.

dontcallmedom/code-talks 1

An HTML-based code displayer, that allows to talk through the creation of a piece of a code (e.g. for a tutorial)

dontcallmedom/android 0

The ownCloud Android App

dontcallmedom/apa 0

Accessible Platform Architectures WG deliverables

push eventw3c/webref

reffy-bot

commit sha ccde09d91aa6384c5f4eef5c8ae4b16e1e953990

Update of ED report from new reffy run Using reffy commit 1016d00df6b59c74f8c3a52f1a30979c3a643baa.

view details

push time in 3 hours

push eventw3c/validate-repos

w3c-validate-repos-bot

commit sha c679de69e66a502eefdf35a55456f836a08e359f

Update report.json, rec-track-repos.json, hr-repos.json

view details

push time in 4 hours

push eventdontcallmedom/webidlpedia

fetch-info bot

commit sha b8308c1b4934770b05ecd89e6bbde3e6bfbc2758

Automatic update

view details

push time in 4 hours

issue commentw3c/oss-relations

Landscape of W3C standards relying on single OSS implementations

ANGLE is perhaps another example. Offhand I think most if not all WebGL implementations rely on it.

dontcallmedom

comment created time in 5 hours

issue commentw3c/webref

Extract HTML/SVG tagname-interface mapping

Reffy has custom code to parse CSS property definitions to generate the css extracts. It makes sense to me to do the same thing with the HTML element definitions, starting with scraping the DOM interface.

That should not require changes to the spec files, but scraping rules will obviously have to follow possible spec conventions changes. The following seems to work:

  1. Retrieve all <dl> element definitions with document.querySelectorAll('.element')
  2. Look for a <dt> whose text is DOM interface:
  3. Following <dd>:
    • has a <pre> with the IDL of the interface (e.g. <p>). Either we fire the Web IDL parser at it, or we look for interface [interface name].
    • OR starts with Uses [interface name] (e.g. <samp> or <col>).
saschanaz

comment created time in 8 hours

push eventw3c/webref

reffy-bot

commit sha 797d4c5d30a0c6c09fc374d5a3e72fe445cabf94

Update of ED report from new reffy run Using reffy commit 1016d00df6b59c74f8c3a52f1a30979c3a643baa.

view details

push time in 9 hours

issue openedw3c/webref

Extract HTML/SVG tagnames

Background: https://github.com/saschanaz/types-web/issues/76

It would probably requires some changes to the spec files.

created time in 9 hours

issue commentw3c/webref

Publish CSS bits as @webref/css

Sounds reasonable. I'm okay with properties only as I already have machineries to generate IDL.

foolip

comment created time in 10 hours

push eventdontcallmedom/webidlpedia

fetch-info bot

commit sha b193c3d2e5ea4fb057ea4d002bce1caa9f704a0b

Automatic update

view details

push time in 10 hours

issue commentw3c/webref

Publish CSS bits as @webref/css

I misread what I responded to. I don't have a need for the IDL-as-text at all, but having it all as a single block seems less useful than having a block per spec.

The main reason I don't need the IDL-as-text is that mdn-bcd-collector also adds lots of non-standard CSS properties, and I want to generate the same kinds of tests for those. Thus I need to start with property names and generate IDL or tests from those.

foolip

comment created time in 10 hours

issue commentw3c/webref

Publish CSS bits as @webref/css

I also don't think having all the generated IDL as a single block would be useful.

You mean you want multiple blocks? 👀

foolip

comment created time in 13 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 55731c5933e3264e86809502f8ca6e9cfab4f39b

Update repo map

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 79104a102dbadd2485438aa38878a636e3264561

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 9eb29d218fb65d4425e32c4e0d05bc1f851868ce

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 77b500fa201a5c0fc28179dfe3cec88c90ebd638

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 2f4454a5079efa4f4c357704959954b0f683cea8

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha b8932c78f599df4860c1a978df73abf9c9715602

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha fbe953a3c10ec2a8b0e14ebc7b26ee3278789815

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha e04637d202ca8d20846b3b862c69dbccf80d632e

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 9c84fb90abcab0feee4771d26c6dcbb083004429

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha cfc8ad9d870b80a4f6c6ce2baab0a17567978144

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha b2a5c330fa6846d008dc5536f61b309b593128a0

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 50c1ccdd56bf3ca1e6543a4856231111efdb295a

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 517d57117fd506721fa4b0a3610bc6abed797277

Update from Github

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 04c2d227f35f1f06b79cfcdaa1d69717d767d492

Update from spreadsheets

view details

push time in 15 hours

push eventw3c/spec-dashboard

Dom's bot

commit sha 9d532dc970c6a19693e228ec66fc081ae69780d6

Update from TR

view details

push time in 15 hours

push eventw3c/webref

reffy-bot

commit sha 0c206818a4f3bda0056a23a44a2d2aa89cc40f13

Update of ED report from new reffy run Using reffy commit 7ca4afbd8fb80d40217d3fffb4df529814ddf427.

view details

push time in 15 hours

push eventdontcallmedom/webidlpedia

fetch-info bot

commit sha 020b07b7ad9d0cc4aa0702bd324179bcd1222064

Automatic update

view details

push time in 16 hours

Pull request review commentw3c/webref

Add logic to create @webref/css package

+From 9be95c0f7f61ad2ffd296a9346c552ae05b3f519 Mon Sep 17 00:00:00 2001+From: Francois Daoust <fd@tidoust.net>+Date: Thu, 4 Mar 2021 17:00:07 +0100+Subject: [PATCH] Separate stacked combinators++The parser does not support stacked combinators, see discussion in:+https://github.com/w3c/reffy/issues/494#issuecomment-790713119

I don't think I'll have the bandwidth to look into that in the next few days, but please do :)

tidoust

comment created time in 17 hours

issue commentw3c/webref

Publish CSS bits as @webref/css

Or are there scenarios where it would be useful to have the CSSOM generated IDL per spec?

Not in my mind.

I also don't think having all the generated IDL as a single block would be useful.

foolip

comment created time in 17 hours