Page 1 of 1
| Uploaded | Revised | By | Comment | 2023-12-11 |
|---|---|---|---|---|
| 13:53:11 PST | 2023-11-13 13:30:47 PST | fantasai | [css-counter-styles] Require i18n's Ready-Made Counter Styles #8636 (#9596) https://github.com/w3c/csswg-drafts/issues/8636#issuecomment-1591665495 https://lists.w3.org/Archives/Public/www-style/2023Jun/0003.html | |
| 13:53:11 PST | 2023-11-13 13:30:47 PST | fantasai | [css-counter-styles] Require i18n's Ready-Made Counter Styles #8636 (#9596) https://github.com/w3c/csswg-drafts/issues/8636#issuecomment-1591665495 https://lists.w3.org/Archives/Public/www-style/2023Jun/0003.html | |
| 13:53:11 PST | 2023-11-13 13:30:47 PST | fantasai | [css-counter-styles] Require i18n's Ready-Made Counter Styles #8636 (#9596) https://github.com/w3c/csswg-drafts/issues/8636#issuecomment-1591665495 https://lists.w3.org/Archives/Public/www-style/2023Jun/0003.html | 2023-12-18 |
| 12:43:44 PST | 2023-12-18 12:43:06 PST | fantasai | [meta] Consistent spelling of lowercase/uppercase | 2023-06-07 |
| 08:02:17 PDT | 2023-05-25 15:17:23 PDT | tabatkins | [css-counter-styles-3][editorial] Rephrase the OM descriptor parsing to use the CSS/parse algorithm rather than doing using bespoke language. #7040 | 2022-08-08 |
| 11:48:26 PDT | 2022-08-08 11:47:58 PDT | tabatkins | [css-counter-styles-3][editorial] fix markup, fixes #7565 | 2021-07-22 |
| 22:56:05 PDT | 2021-07-22 22:55:44 PDT | fuqiao_xue | [css-counter-styles-3] Update Previous Versions | 2021-07-15 |
| 15:44:58 PDT | 2021-07-15 15:44:22 PDT | heycam | [css-counter-styles-3] Remove unnecessary semicolons from productions | 2021-06-08 |
| 12:02:25 PDT | 2021-06-08 12:01:47 PDT | fantasai | [css-counter-styles-3] Update title of i18n NOTE in cross-reference. https://github.com/w3c/i18n-request/issues/157#issuecomment-856947561 | 2021-06-03 |
| 18:15:45 PDT | 2021-06-03 18:15:22 PDT | fantasai | [css-counter-styles-3] Fix links | |
| 17:56:57 PDT | 2021-06-03 17:56:32 PDT | fantasai | [css-counter-styles-3] Fix links | |
| 17:08:26 PDT | 2021-06-03 17:07:45 PDT | fantasai | [css-counter-styles-3] Update Changes list | |
| 16:58:37 PDT | 2021-06-03 16:58:16 PDT | tabatkins | [css-counter-styles-3] Allow UAs to render the symbolic styles in a UA-chosen font, as well. #6201 | |
| 16:52:35 PDT | 2021-06-03 16:52:08 PDT | tabatkins | [css-counter-styles-3] Make all the predefined symbolics non-overrideable, and specify that extending them uses the spec version, not the UA exception. #3584 | 2021-05-17 |
| 14:26:46 PDT | 2021-05-17 14:24:15 PDT | dbaron | Revert "Revert "Merge branch 'main' of https://github.com/w3c/csswg-drafts into main"" This reverts commit 9d14c2393cfeca05c799d43444fe9c860074e80b. The commit that it was reverting was actually fine; it was a merge, but looked like it was bad because it had a large diff against the first parent but it had no diff against the second (which was the relevant one in a "linear history" of this repository). | |
| 13:52:15 PDT | 2021-05-17 12:25:01 PDT | adam_argyle | Revert "Merge branch 'main' of https://github.com/w3c/csswg-drafts into main" This reverts commit 442ca50fbfe14f5e163336a54844ba447d2bafa7, reversing changes made to d0337ce2a834e083954a3b090fd69ea918a0302a. | 2021-05-14 |
| 12:42:36 PDT | 2021-05-14 12:42:13 PDT | tabatkins | [css-counter-styles-3] Whoops, previous edit was wrong. Just catch the 0-value case directly. #5784 | |
| 12:01:08 PDT | 2021-05-14 12:00:20 PDT | tabatkins | [css-counter-styles-3] Remove 'weight > value' check; it's not technically necessary, and it trips the assert. #5784 | 2021-05-13 |
| 17:24:30 PDT | 2021-05-13 17:24:06 PDT | tabatkins | [css-counter-styles-3] Define that counter styles are tree-scoped. #5693 | |
| 16:31:44 PDT | 2021-05-13 16:31:18 PDT | fantasai | [css-counter-styles-3] Clarify that speak-as represents spoken output. It may be used for other AT. #6040 | |
| 16:01:26 PDT | 2021-05-13 16:01:02 PDT | tabatkins | [css-counter-styles-3] Rewrite the additive representation algo. This is partially for style, but also properly handles the case where you hit a 0-weight symbol when there's still value left. Fixes #5784. | |
| 15:29:53 PDT | 2021-05-13 15:29:30 PDT | tabatkins | [css-counter-styles-3] Make it clearer that 'numbers' uses the numeric value. Specify some obvious conditions for when words/spell-out should fall back. | |
| 14:55:24 PDT | 2021-05-13 14:55:01 PDT | tabatkins | [css-counter-styles] Remove more mentions of insufficient 'symbols' length making things invalid, and put an explainer about the length req into 'system' as well. Fixes #5717. | |
| 14:49:32 PDT | 2021-05-13 14:49:06 PDT | tabatkins | [css-counter-styles-3] A too-short 'symbols' descriptor just makes it not define a counter style, not invalid. Fixes #5698. | |
| 14:45:48 PDT | 2021-05-13 14:45:19 PDT | tabatkins | [css-counter-styles-3][editorial] Just use 'defined', not 'currently-defined', to avoid any implication of temporality. Fixes #4205. | 2021-04-28 |
| 10:34:19 PDT | 2021-04-28 10:33:36 PDT | tabatkins | [css-counter-styles-3] Per WG resolution, change the example character for 'square' style to be U+25AA. Fixes #6200. | 2021-04-08 |
| 22:08:13 PDT | 2021-04-08 22:06:02 PDT | florian | Use consistant capitalization for "user agent" Also checks in a little script that helps in doing this semi-automatically. | 2021-02-21 |
| 23:27:15 PST | 2021-02-21 23:26:51 PST | fantasai | fix: typos across specs (#5992) | 2020-03-10 |
| 08:58:04 PDT | 2020-03-10 08:57:47 PDT | AmeliaBR | Use bracket range notation in syntax grammar [css-values-3][css? (#3894) * [css-values-3] Tidy bracket range definition - Fix incorrect heading level & a typo from 8ea8d7d35f833d08d3cd7a4681618519960da821 - Add examples converting the notation to prose. * [css-values-4] Copy over bracket range definition These changes were added to Level 3 in 8ea8d7d35f833d08d3cd7a4681618519960da821 and 1265976bd6edbc8b8d5ca039ef19b472fcb890f3 (And fix a tabs-vs-spaces error that bikeshed was choking on.) * [css-backgrounds-3][css-backgrounds-4] Use bracketed range notation Added bracketed range notation for non-negative values ( [0,?] ) in these properties & productions: - <bg-size> - <line-width> - border-radius and longhands - border-image-slice - border-image-width - border-image-outset - <shadow> NOTE: required re-writing the syntax (since ony one of the 4 possible lengths has a restriction) - border-limit and border-clip in level 4 NOTE: these didn't have prose restrictions, but they also didn't explain how negative values could work. I added a changes note to level 3 (change since CR), but not level 4 (not published yet). * [css-values-3][css-values-4] Export dfn for bracketed range notation * [css-multicol-1][css-multicol-2] Use bracketed range notation Added bracketed range notation for non-negative values ( [0,?] ) or strictly positive integers ( [1,?] ) in these properties: - column-width - column-count - column-gap - column-span (level 2) For column-rule-width, the syntax change was made for the `<line-width>` production, in 933d7dd5b913ad7f8090eb6f4eeba577911d3e64 * [css-flexbox-1] Use bracketed range notation Added bracketed range notation for non-negative values ( [0,?] ) in these properties: - flex-grow - flex-shrink Also use it in the prose descriptions for `flex`, and to replace the made up `<postive-number>` variable in the examples of common patterns. Created a new "Changes since the 19 November 2018 CR" section to include a mention of the update. The syntax for `flex-basis` will be updated by reference when `width` is updated. * [css-counter-styles-3] Use bracketed range notation Added bracketed range notation for non-negative values ( [0,?] ) in the following descriptors: - pad - additive-symbols Note: I didn't add any restriction to the integer in the `system: fixed <integer>` descriptor, since there was no prose constraint. But I'm not sure that negative values make sense here. * Standardize prose for constrained values [css-backgrounds-3][css-counter-styles-3][css-flexbox-1][css-multicol-1][css-values-3][css-values-4] For all the specs covered by PR #3894. <<type [0,∞]>> ? ?Negative values are not allowed.? <<integer [1, ∞]>> ? ?Values must be greater than 0.? And remove some duplicate phrases. Added these phrases & the other most commonly used one (?are invalid?) to the note in CSS Values about prose restrictions. * [css-values-3][css-values-4] Fix broken entity Co-authored-by: Tab Atkins Jr <jackalmage@gmail.com> | 2019-12-06 |
| 07:57:21 PST | 2019-12-06 07:56:49 PST | fuqiao_xue | [css-counter-styles-3] Change cjk-earthly-branch and cjk-heavenly-stem to fixed | 2019-08-16 |
| 19:29:06 PDT | 2019-08-16 19:28:42 PDT | fantasai | [css-lists-3][css-counter-styles-3] Update / bifurcate acknowledgements. | 2019-07-29 |
| 15:53:42 PDT | 2019-06-29 15:25:35 PDT | tabatkins | [css-counter-styles-3] Fix <counter-style> syntax to refer to <symbols()> instead of defining it | 2018-12-09 |
| 21:14:23 PST | 2018-12-09 21:13:58 PST | fuqiao_xue | Remove some references to Bugzilla | 2018-02-22 |
| 14:05:39 PST | 2018-02-21 20:43:25 PST | ericwilligers | CSSFontFaceRule etc. exposed to Window CSSFontFaceRule, CSSViewportRule, CSSCounterStyleRule are now explicitly exposed to Window. The other CSSRule interfaces defined in csswg-drafts are already exposed to Window. resolves #2342 | 2018-01-24 |
| 20:02:02 PST | 2017-12-20 05:42:22 PST | fuqiao_xue | Use autolink for HTML elements | 2017-12-04 |
| 11:49:32 PST | 2017-12-04 11:49:13 PST | tabatkins | [css-counter-styles] minor link fixup | |
| 11:26:30 PST | 2017-12-04 11:26:07 PST | tabatkins | [css-counter-styles] Mark <image> in <symbol> as at-risk, as there are no implementation plans yet. Related to #1991. | 2017-11-14 |
| 15:38:14 PST | 2017-11-14 15:37:45 PST | tabatkins | [css-counter-styles][meta] Fix markup. | |
| 15:26:40 PST | 2017-11-14 15:26:23 PST | tabatkins | [css-counter-styles] @counter-style with missing descriptors just fails to define a counter style, but is otherwise treated as valid. Fixes #1682. | 2017-11-09 |
| 16:14:17 PST | 2017-11-09 16:12:58 PST | dbaron | Add w3cid metadata for all editors. I got the uids from the "Edit status" links in https://www.w3.org/2000/09/dbwg/details?group=32061 and made the actual changes with a python script. | 2017-10-25 |
| 16:52:19 PDT | 2017-10-25 16:14:48 PDT | tantek_celik | Use Title: meta instead of explicit <h1> | 2017-10-11 |
| 14:48:05 PDT | 2017-10-11 14:47:55 PDT | tabatkins | THE GREAT NUMBERING - put all specs into numbered directories, per WG resolution, and use Shepherd to set which level is currently shown for the unleveled url. |