| 04:23 | <Domenic> | annevk: post-holiday ping on https://github.com/whatwg/html/pull/10005 |
| 10:02 | <annevk> | PSA: If you see a spam PR or issue, please label it with invalid. That's a label recognized by GitHub's tooling and I'm in the process of adding it to all the repositories of WHATWG standards. |
| 14:29 | <chargeitall> | why default is written twice? |
| 14:52 | <zcorpan> | "default value" is a placeholder |
| 14:53 | <chargeitall> | why it is not written with italic like the parameter placeholder ? |
| 14:56 | <zcorpan> | "parameter" is a placeholder for a variable name. See the example below. |
| 15:07 | <chargeitall> | the example below is for an algorithm parameter not a variable parameter. A variable is declared with "let" and changed with "set" |
| 15:30 | <chargeitall> | ..., be a new list. ..., be null. ..., is a string. ..., is true. after verb to be there is no italic except for ..., be target why? |
| 15:44 | <annevk> | Because target is a variable and the others are not? |
| 15:45 | <annevk> | Although it seems there's a bug there as the second instance of target doesn't have italics. |
| 15:47 | <chargeitall> | yes. |
| 15:51 | <chargeitall> | To clarify, you are uncertain whether to use italics for the second instance of target? |
| 15:52 | <annevk> | I'm not, it should be italics. |
| 15:53 | <chargeitall> | okay |
| 16:00 | <chargeitall> | Do you create issue for each bug you encounter? |
| 16:09 | <annevk> | It's fine to create a PR directly, just make sure you can sign the agreement. |
| 16:13 | <zcorpan> | OK yes, but does the example make it clearer why one of them is italic? |
| 16:14 | <chargeitall> | I have never done this. I need to google it first |