Page 1 of 1
| Uploaded | Revised | By | Comment | 2024-07-29 |
|---|---|---|---|---|
| 07:54:06 PDT | 2024-07-29 07:53:45 PDT | florian | [css-nav-1] Fix spurious / in <img> (#10630) | 2023-03-01 |
| 14:08:26 PST | 2023-03-01 14:08:02 PST | tabatkins | [css-nav-1] Define properties with animation type (#8422) | 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-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. | 2020-11-09 |
| 12:55:30 PST | 2020-11-09 12:55:09 PST | fantasai | s/privsec/priv-sec/g for consistency. (priv-sec was most prevalent) | 2020-09-18 |
| 15:42:57 PDT | 2020-09-18 14:48:54 PDT | SebastianZ | Removed duplicate "keywords" from Value Definitions section | 2020-08-18 |
| 14:13:10 PDT | 2020-08-18 09:33:43 PDT | autokagami | [css-nav-1] Align with Web IDL specification | 2020-04-01 |
| 21:05:55 PDT | 2020-04-01 20:15:48 PDT | dbaron | [css-nav-1] Spell check. | 2020-02-22 |
| 08:36:08 PST | 2020-02-22 08:35:50 PST | autokagami | [css-nav-1] Align with Web IDL specification (#4798) | 2020-01-16 |
| 16:21:27 PST | 2020-01-16 16:20:52 PST | fantasai | [meta] Align value definition reference across all specs. Use more obvious heading. Include link to definition syntax directly. #1397 | 2020-01-14 |
| 12:57:18 PST | 2020-01-14 12:56:40 PST | tabatkins | [various] Editorial link fixes (and some incidental ws fixes). | 2019-11-26 |
| 16:59:11 PST | 2019-11-26 16:58:50 PST | jh.hong | [css-nav-1] Fix indentation error | |
| 01:29:41 PST | 2019-11-26 01:29:16 PST | jh.hong | [css-nav-1] Add a link to the newly published wd | 2019-11-25 |
| 22:35:43 PST | 2019-11-25 22:35:18 PST | jh.hong | [css-nav-1] Add a link for the previous version | |
| 21:37:29 PST | 2019-11-25 21:36:55 PST | jh.hong | [css-nav-1] Fix errors from HTML validator | |
| 20:51:28 PST | 2019-11-25 20:51:02 PST | jh.hong | [css-nav-1] Fix broken URI fragments | |
| 18:21:53 PST | 2019-11-25 18:21:29 PST | jh.hong | [css-nav-1] Add the change section | |
| 01:33:40 PST | 2019-11-25 01:33:15 PST | jh.hong | [css-nav-1] Fix the mistake in processing model If the best candidate is found, "navbeforefocus" event should be fired. (not "navnotarget") | |
| 01:23:14 PST | 2019-11-25 01:18:38 PST | jh.hong | [css-nav-1] Fix the typo error | 2019-11-20 |
| 18:28:03 PST | 2019-11-20 18:20:49 PST | jh.hong | Merge remote-tracking branch 'upstream/master' into improve-processing-model | 2019-11-11 |
| 22:35:31 PST | 2019-11-11 22:35:05 PST | jh.hong | [css-nav-1] Drop `inside` option from spatialNavigationSearch API Drop `inside` option from `spatialNavigationSearch` because it's risky | 2019-11-07 |
| 21:25:34 PST | 2019-11-07 21:25:10 PST | jh.hong | [css-nav-1] Modify how to select candidates for partially overlapped case Modify the way to select candidates for partially overlapped element with the search origin element. More detail condition about how elements are overlapped leaves to the UA. | |
| 17:44:21 PST | 2019-11-07 17:43:52 PST | jh.hong | [css-nav-1] Change the image files (to transparent) | 2019-11-06 |
| 20:47:23 PST | 2019-11-06 20:46:43 PST | jh.hong | [css-nav-1] Modify the inheritance of spatial-navigation-function Reason: This property is equivalent with `spatial-navigation-action` in terms of inheritance feature | 2019-11-05 |
| 02:11:02 PST | 2019-11-05 02:01:45 PST | jh.hong | [css-nav-1] Fix the markup for hiding API description | 2019-11-04 |
| 23:58:03 PST | 2019-11-04 23:57:43 PST | jh.hong | [css-nav-1] Fix link errors | |
| 23:49:49 PST | 2019-11-04 23:49:28 PST | jh.hong | [css-nav-1] Fix the indentation error | |
| 22:59:16 PST | 2019-11-04 22:58:52 PST | jh.hong | Modify the description of spatialNavigationSearch() | |
| 22:04:56 PST | 2019-11-04 22:04:36 PST | jh.hong | Modify the description of focusableArea * Remove redundant description (Finding focusable areas already returns DOM anchor, therefore `anchor` variable isn't necessary.) | |
| 22:00:02 PST | 2019-11-04 21:59:40 PST | jh.hong | [css-nav-1] Minor expression changes | 2019-09-30 |
| 21:32:34 PDT | 2019-09-30 17:42:37 PDT | jh.hong | [css-nav-1] Tweak description of the example | 2019-09-27 |
| 00:57:55 PDT | 2019-09-27 00:57:29 PDT | jh.hong | [css-nav-1] Clear description about updating search origin Make the process of updating search origin more clear, depending on the discussion in https://github.com/w3c/csswg-drafts/pull/4309 | |
| 00:42:43 PDT | 2019-09-27 00:42:19 PDT | jh.hong | [css-nav-1] Modify IDL of spatialNavigationSearch Related to https://github.com/w3c/csswg-drafts/issues/3743 | 2019-09-25 |
| 01:34:48 PDT | 2019-09-25 01:34:23 PDT | jh.hong | [css-nav-1] Fix the wrong description Fix the wrong description about selecting the candidate which doesn't overlap with search origin before measuring the distance. | |
| 01:20:57 PDT | 2019-09-24 00:17:13 PDT | jh.hong | [css-nav-1] Fix the unreachability for a focusable element inside the search origin Consider the focusable element which fully overlaps with another focusable element. Detailed changes are as below: 1. Add another condition to the definition of 'inside area' * To consider the focusable element which fully overlaps with search origin as a candidate for enabling the focus to move there. 2. Make the difference the way to select 'insider' depending on wheather the search origin is a spatial navigation container or not * If the search origin is container, consider the partially visible focusables as the insider. * Else (if the search origin is the general element), consider only the fully overlapped focusables as the insider. * NOTE: The partially overlapped focusable isn't included in the set of insider. 3. Modify the way to select candidates among visible focusable elements * To measure the distance from the elements which is outside to the search origin. Close https://github.com/w3c/csswg-drafts/issues/3386 | 2019-09-23 |
| 01:38:40 PDT | 2019-09-23 01:36:38 PDT | jh.hong | [css-nav-1] Simplify the description of processing model Hide the description related to css property (`spatial-navigation-action`) from the processing model by option | 2019-09-22 |
| 18:51:35 PDT | 2019-09-15 18:27:17 PDT | jh.hong | [css-nav-1] Update the search origin after scrolling The search origin will be updated only when the old focus target is completely off-screen after the scrolling. (Note: If the old focus target is partially in the view after scrolling, the search origin won't be changed) Related issue: https://github.com/w3c/csswg-drafts/issues/3392 | 2019-09-15 |
| 17:47:18 PDT | 2019-09-15 17:47:07 PDT | jh.hong | [css-nav-1] Add the link for updating the search origin step | 2019-09-10 |
| 19:25:30 PDT | 2019-09-10 19:25:07 PDT | jh.hong | [css-nav-1] Modiy more precise description for setting search origin | 2019-09-06 |
| 01:32:58 PDT | 2019-09-06 01:32:37 PDT | jh.hong | [css-nav-1] Fix a link error | |
| 01:28:38 PDT | 2019-09-06 01:28:13 PDT | jh.hong | [css-nav-1] More precise description when the focus target loses the focus Search origin should be set again if the focus target loses the focus. More detailed cases are (1) the focus target removed from the page (2) the focus target becomes invisible or disabled Therefore, more description about above cases had been added. (1) Remove Reference: * https://html.spec.whatwg.org/#data-model * https://html.spec.whatwg.org/multipage/infrastructure.html#nodes-are-removed | 2019-09-05 |
| 06:41:30 PDT | 2019-09-05 06:41:08 PDT | jh.hong | [css-nav-1] Add more details about how to set the search origin * Add how to set the search origin depending on its status change * Add precise definition about `search origin` and `spatial navigation starting point` * Seperate the "set the search origin" step from the processing model * related to https://github.com/w3c/csswg-drafts/issues/3391 | 2019-08-02 |
| 01:45:46 PDT | 2019-08-02 01:44:43 PDT | jh.hong | [css-nav-1] Add the name to the argument Add the name to the argument for clearer reference | 2019-08-01 |
| 03:10:29 PDT | 2019-08-01 03:10:03 PDT | jh.hong | [css-nav-1] Define the inside area in general Define "inside area" in general and use that term elsewhere. | 2019-06-20 |
| 19:09:35 PDT | 2019-06-20 19:09:18 PDT | jh.hong | [css-nav-1] Fix the link error | |
| 19:07:20 PDT | 2019-06-20 19:07:00 PDT | jh.hong | [css-nav-1] Fix and upate the description Update the description about `spatial-navigation-function` | |
| 02:00:50 PDT | 2019-06-20 01:58:53 PDT | jh.hong | [css-nav-1] Add spatial-navigation-function CSS property During the CSS WG F2F, it was resolved to add `spatial-navigation-function` CSS property. This property is used for setting the focus navigation algorithm with the predefined values. Close https://github.com/w3c/csswg-drafts/issues/3964 | 2019-06-13 |
| 02:57:03 PDT | 2019-06-13 02:56:39 PDT | jh.hong | [css-nav-1] Modify the condition of candidates for custom spatial navigation container Close https://github.com/w3c/csswg-drafts/issues/3965 | 2019-06-07 |
| 11:10:18 PDT | 2019-06-07 11:09:41 PDT | dbaron | Add w3cids for editors. | 2019-05-08 |
| 01:32:06 PDT | 2019-05-08 01:31:43 PDT | jh.hong | [css-nav-1] Fix `alignBias` definition Fix the mistake about `alignBias` definition depending on the original proposal. (+ Remove trailing spaces) Reference: - https://wicg.github.io/spatial-navigation/tests/ux/result.html#2-add-the-factor-about-calculating-the-degree-of-alignment-between-a-candidate-and-the-search-origin - w3c#3388 (comment) | 2019-04-25 |
| 19:46:00 PDT | 2019-04-25 19:45:37 PDT | jh.hong | [css-nav-1] Change the result of getSpatialNavigationContainer() Relate to: https://github.com/w3c/csswg-drafts/issues/3743#issuecomment-486160981 | 2019-04-23 |
| 16:48:30 PDT | 2019-04-23 16:48:09 PDT | jh.hong | [css-nav-1] Add the link of published draft | 2019-04-07 |
| 23:25:31 PDT | 2019-04-07 23:25:07 PDT | jh.hong | [css-nav-1] Fix a link error | 2019-04-05 |
| 02:21:41 PDT | 2019-04-04 23:36:42 PDT | florian | [css-nav-1] Clarify how the improve distance function works | 2019-04-03 |
| 19:11:53 PDT | 2019-04-03 19:11:26 PDT | jh.hong | Merge branch 'master' into add-spatnav-action | |
| 18:21:37 PDT | 2019-04-03 01:20:43 PDT | jh.hong | Fix link errors | 2019-03-28 |
| 23:41:17 PDT | 2019-03-28 23:40:32 PDT | jh.hong | Merge branch 'master' into improve-distance-function | 2019-03-25 |
| 23:03:22 PDT | 2019-03-25 23:03:09 PDT | jh.hong | Merge pull request #3729 from jihyerish/drop-navbeforescroll [css-nav-1] Drop navbeforescroll event | |
| 19:14:19 PDT | 2019-03-25 19:10:13 PDT | jh.hong | [css-nav-1] Modify the explanation about focusableAreas * Modify the method steps of the API * Add an example of the API | 2019-02-25 |
| 21:56:09 PST | 2019-02-25 21:55:50 PST | florian | [css-nav-1] Mention open issue on naming the window.navigate API | 2018-12-04 |
| 16:20:50 PST | 2018-12-04 16:08:05 PST | jh.hong | [css-nav-1] Update the status of issues - Remove the resolved issue (#28 in WICG) - Fix the link of the issue from WICG repo to CSSWG repo | |
| 01:31:35 PST | 2018-12-04 01:30:17 PST | florian | [css-nav-1] Delete stale issue Shadow DOM is not explicitely mentioend, but it is taken into account via the various algorithms that the spec invokes, such as event dispatching. | |
| 01:22:57 PST | 2018-12-04 01:21:10 PST | florian | [css-nav-1] Gate the navigation events on a policy-controlled feature Closes #3390 | 2018-12-03 |
| 22:42:20 PST | 2018-12-03 22:41:01 PST | florian | [css-nav-1] Disambiguate between two similar terms Closes #3389 | |
| 00:22:12 PST | 2018-12-03 00:21:13 PST | florian | [css-nav-1] Remove link to old issue tracker All open issues have been migrated, no need to keep pointing people to it. | 2018-11-15 |
| 21:20:03 PST | 2018-11-15 21:19:41 PST | florian | [css-nav-1] Conform to typical CSS spec naming conventions | |
| 20:59:55 PST | 2018-11-15 00:25:33 PST | florian | [css-nav-1] Update metadata This is a csswg spec now, update metadata accordingly |