profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/chicoxyzzy/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.
Sergey Rubanov chicoxyzzy Helping @tc39 and striving to bring @WebAssembly to your web browser. Working on standards and tools on my spare time. Wanna do it full-time. 🤖. he/him

acdlite/redux-rx 1019

RxJS utilities for Redux.

chicoxyzzy/ambry 23

:package: WebStorage wrapper that makes your life easier

chicoxyzzy/babel-plugin-dynamic-import-system-import 7

Babel plugin to transpile import() to System.import()

chernivtsijs/webassembly-simplified 4

"Просто о WebAssembly" by @chicoxyzzy

chicoxyzzy/10-years-of-frontend 0

Больше 10 лет фронтенда

chicoxyzzy/2017.rustfest.eu 0

The website for RustFest 2017

chicoxyzzy/admin 0

Group administration

chicoxyzzy/agendas 0

TC39 meeting agendas

chicoxyzzy/annotations 0

Proposal for Custom Annotation Syntax in the Text Format

chicoxyzzy/assemblyscript 0

A TypeScript to WebAssembly compiler 🚀

issue commentmdn/content

Issue with "URL()": Dont work with sftp in tsx

OK yeah it seems that for non-special URL schemes, Firefox and Chrome don’t return the username and password as expected.

Transferring this to the BCD repo. I guess we should mark the relevant Firefox and Chrome entries as partial_implementation, with notes.

mranosa

comment created time in a few seconds

issue commentmdn/content

Issue with "Test your skills: HTML text basics": (short summary here please)

@Mucunguzi256 I don't understand what you are reporting, as there are not any CodePens in the content you refer to.

Your CodePen doesn't have any styling for headings in it. So I'm not really sure how to help. If you are looking for help working through the examples then post here: https://discourse.mozilla.org/c/mdn/236

@NegiAkash890 please raise a new ticket for any problem, I also don't understand your report as there appear to be two missign images. Please open a new ticket with all the information and I'll take a look.

Mucunguzi256

comment created time in a few seconds

push eventweb-platform-tests/wpt

François Daoust

commit sha 83e82630d4af4e1c31c03c1cfc3b424d7f805ab4

Update URL for MathML Core (#29358) Spec now developed by Math Working Group. Repository moved to W3C organization accordingly.

view details

push time in 2 minutes

PR merged web-platform-tests/wpt

Reviewers
Update URL for MathML Core mathml wg-math

Spec now developed by Math Working Group. Repository moved to W3C organization accordingly.

+1 -1

0 comment

1 changed file

tidoust

pr closed time in 2 minutes

pull request commentnodejs/node

src,url: separate some tables out of node_url.cc

As an alternative to a new *.cc file, these could be moved into a node_url-inl.h header

Because it's real data, not only declaration. If node_url-inl.h is mis-included by another file, the compilation will failed. So I think it's better to be stored in a *.cc file.

Should we add a TODO comment to move the variables to node_url-inl.h when #38807 lands because in C++17 we can inline variables?

All we’d get out of that is probably just longer compilation times. @XadillaX is right, this is actual data that is accessed as data, so inlining has no benefit here and putting it in a .cc file is just the right thing to do, and I don’t understand why something else would be suggested here.

XadillaX

comment created time in 3 minutes

pull request commentnodejs/node

src,url: separate some tables out of node_url.cc

As an alternative to a new *.cc file, these could be moved into a node_url-inl.h header

Because it's real data, not only declaration. If node_url-inl.h is mis-included by another file, the compilation will failed. So I think it's better to be stored in a *.cc file.

Should we add a TODO comment to move the variables to node_url-inl.h when https://github.com/nodejs/node/pull/38807 lands because in C++17 we can inline variables?

XadillaX

comment created time in 6 minutes

pull request commentnodejs/node

test: improve buffer coverage

CI: https://ci.nodejs.org/job/node-test-pull-request/38624/

pd4d10

comment created time in 6 minutes

push eventweb-platform-tests/wpt

Guido Urdaneta

commit sha e1a723314f3c43edd94758ddba0e5dd715e352f7

[BreakoutBox] Stop MSTGenerator in test MediaStreamTrackProcessor-video.https.html was faling on the WebKit Linux Leak bot due to a generator not being closed. Change-Id: I72d56611ec419fa0d700bd1bf0803ed007d3a46d Fixed: 1219040 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2960248 Commit-Queue: Roberto Carrillo <robertocn@chromium.org> Reviewed-by: Roberto Carrillo <robertocn@chromium.org> Cr-Commit-Position: refs/heads/master@{#891990}

view details

push time in 7 minutes

created tagweb-platform-tests/wpt

tagepochs/three_hourly/2021-06-14_09H

Test suites for Web platform specs — including WHATWG, W3C, and others

created time in 7 minutes

push eventweb-platform-tests/wpt

Raymond Toy

commit sha e888fa12c505ad2793fac96ab3158e42e861bf84

Update test and move cancelAndHold test to WPT First add tests to cancelAndHoldAtTime for negative and non-finite values to verify that the correct error is thrown. Second, move the test to WPT. Manually verified that Safari passes this test. Firefox fails because it doesn't have cancelAndHoldAtTime yet. Bug: 1212672 Change-Id: I0c2efdc0deacc6e1d12caa17d6993bd99fccb709 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2912306 Reviewed-by: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Raymond Toy <rtoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#886364}

view details

Alison Maher

commit sha bc6aa2df9438b02a2be08efb88db022e6943217c

Forced accent-color followup In CL:2847031, accent-color was forced to auto in forced colors mode. This CL moves this logic to StyleAdjuster::AdjustForForcedColorsMode() so that it is forced in the same place as the other properties forced at computed value time. Bug: 1092093 Change-Id: I77ba92e30c6ea060521a8d05747c32a38f149601 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2909975 Reviewed-by: Joey Arhar <jarhar@chromium.org> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/master@{#886369}

view details

Rune Lillesveen

commit sha 2ea42e4e13cc9ca219ba7b2b4cca39ab34f438a7

Preload background-image resources in tests Preload and wait for background-image resources to finish loading before triggering reftest screenshots. Background images are triggered to load the first time we do a style resolution which means it is not guaranteed to be loaded and painted on first paint. These tests are flaky, and increasingly so with [1]. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2871469 Bug: 332189 Change-Id: Ibefbd75f22a9783e27838ec549072a58ede31325 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2916998 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#886469}

view details

Kagami Sascha Rosylight

commit sha f4d53916c5b99642a3ab5267e000a1988ca94bae

Defer SetMaxLength in SetValueFromSetRangeText Capping selection range in SetValue early makes the subsequent SetSelectionRange call unable to detect actual selection range change. This patch defers it so that select events can be consistently fired. Differential Revision: https://phabricator.services.mozilla.com/D115729 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1712255 gecko-commit: d97093bef6913a2771713e2db2d80bb0b1d69627 gecko-reviewers: masayuki

view details

Mats Palmgren

commit sha c142d0ed469ea5dec86fdd00a61c2935b4e90623

Remove nscoord assertion that produce false positives. Differential Revision: https://phabricator.services.mozilla.com/D114633 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1474774 gecko-commit: bc593b46778ce2a39b4e62ac0d95814499b05daa gecko-reviewers: dholbert

view details

Kurt Catti-Schmidt (SCHMIDT)

commit sha 0895a4d4a2681c4d892bfeb90cc8188db75cbce0

[GridNG] Updating grid-baseline-align-cycles-001.html This CL updates this test to match expectations where baseline alignment should not apply. The CSS Grid spec indicates that baseline alignment should not apply in cases where there's a cyclic dependency on sizing in the dimension where baseline alignment applies. However, it also states that certain conditions will force another sizing pass, and under such conditions baseline alignment may be possible, and under these circumstances, baseline alignment should apply. If we were to change behavior to match this test case, numerous other second pass baseline tests would break. In fact, this test was actually matching the old expected results before we added logic to support second passes on baseline alignment - see https://chromium-review.googlesource.com/c/chromium/src/+/2873217. Instead, this change updates the test expectations so that they are all situations where baseline alignment should never apply. Bug: 941987 Change-Id: Icec9ec1a2708f488dd2dd0d6c472859b36fb2460 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2911306 Commit-Queue: Kurt Catti-Schmidt <kschmi@microsoft.com> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#886493}

view details

Mason Freed

commit sha 2d8c1c7879def7096951b842a1b8751317b1e621

Update DCHECK for corner case In a corner case situation (crbug.com/1212619) foster parenting can lead to a call to ParserInsertBefore() with a |next_child| value that has a different parent from |this|. This case was already handled in code, so the DCHECK is updated to allow the newly-discovered corner case. The relevant spec is https://html.spec.whatwg.org/multipage/parsing.html#appropriate-place-for-inserting-a-node from which step 2.5 says: If last table has a parent node, then let adjusted insertion location be inside last table's parent node, immediately before last table, and abort these steps. If, at that point, "inside last table's parent node" is a template element, it isn't exactly clear whether that means a child of template's content document, or the template itself. Fixed: 1212619 Change-Id: Iab914f5c39ab6842d92eeae6134f2f347a851e8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2917760 Reviewed-by: Joey Arhar <jarhar@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/master@{#886561}

view details

Matt Wolenetz

commit sha aa56558b1157151f5f71bc41117d0b69dbb88ace

MSE-in-Workers: Make MediaSource.duration acquire lock to access demuxer Worker JS accessing MediaSource.duration wasn't taking the necessary CrossThreadAttachment lock. It should, so that it can safely access the underlying main-thread-owned demuxer to retrieve its duration. This change refactors MediaSource::duration() so that only the IDL calls it, and both it and all other previous callers of duration() are updated to instead call GetDuration_Locked. duration() calls GetDuration_Locked via the existing MediaSource::RunUnlessElementGoneOrClosingUs() machinery that ensures the call only occurs while it is safe to access the underlying demuxer. Other callers of MediaSource::duration() were already running in the context of that machinery, and are updated to provide the appropriate ExclusiveKey to confirm that contract statically during build (like all the other paths already using that machinery). Bug: 1211551,878133 Change-Id: I44b97e63e2a2bd9473f4cd0fc07bc734b344bf2d Fixed: 1211551 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2909389 Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Reviewed-by: Will Cassella <cassew@google.com> Cr-Commit-Position: refs/heads/master@{#886576}

view details

Ana SollanoKim

commit sha d838b9ed5636932df5e2b0616a152480cccdd3f5

[GridNG] Fix invalidation logic for out of flow items via simplified layout This CL addresses a failure where an absolutely positioned item changed its position dynamically. Previously, a new |containing_block_rect| was not being added nor re-computed in |SimplifiedLayoutAlgorithm| for out of flow items that are children of the grid, thus their position was incorrect. This change computes the new containing block by calling existing helpers in |NGGridLayoutAlgorithm|. As a result, some methods had to be changed and constructors overloaded in order to use what was already computed and stored in |NGGridData|. Bug: 1045599 Change-Id: Ic299a57aa5e69063c6f8d0f39c92772503b15f30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2872591 Commit-Queue: Ana Sollano Kim <ansollan@microsoft.com> Reviewed-by: Ethan Jimenez <ethavar@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com> Cr-Commit-Position: refs/heads/master@{#886600}

view details

Manuel Rego Casasnovas

commit sha 166807bde32a7016420f87397b000a1f10c68c1d

Use PostLayoutBoxFragment() in RecalcChildLayoutOverflow() Use PostLayoutBoxFragment() instead of BoxFragment() in LayoutNGMixin::RecalcChildLayoutOverflow() to avoid hitting the assert in NGPhysicalBoxFragment::OwnerLayoutBox(). This avoids the DCHECK failures when for some reason the fragment tree is out of sync. BUG=1203387 TEST=external/wpt/css/css-tables/crashtests/vertical_percentage_crash.html Change-Id: I957a7b35df4f0179bc8c3d33d2476b86a34a225b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2914881 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Manuel Rego <rego@igalia.com> Cr-Commit-Position: refs/heads/master@{#886646}

view details

Ting-Yu Lin

commit sha 4cc4973e07da150eb22f329e739aa0f49a1961ca

Adjust flex container's overflow area only if there are flex items. The rect `flexItemMarginBoxBounds` is initialized at position (0, 0), not the flex container's content-box origin. Inflating its initial value with flex container's padding is just wrong. Differential Revision: https://phabricator.services.mozilla.com/D115854 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1712496 gecko-commit: 17d9dd4ab6315264bffb7bdaa87c0d4f712be1a6 gecko-reviewers: dholbert

view details

Rune Lillesveen

commit sha 1940839d9b546f4e8e47ca61b4fdf4f365b7bac2

Flake-secure background-attachment test Preload background-image and wait for it to be loaded before doing a screenshot. This test is currently not flaky, but landing [1] would make it start failing. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2871469 Bug: 332189 Change-Id: I87d00c8021c44e405b0f45af72f9b8b20eb5a82f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2917298 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#886673}

view details

Aaron Krajeski

commit sha 6ef44f0365c2b81ae4cd39c6e92f13db9d8ba7ef

Add pixel tests for canvas component transfer filters Implementing new SVG Canvas filter interface as defined here: https://github.com/fserb/canvas2D/blob/master/spec/filters.md As defined in SVG: https://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement Bug: 1169216 Change-Id: I6b984126a8499f1b36db35287e08ed8bf3837918 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2916974 Reviewed-by: Yi Xu <yiyix@chromium.org> Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#886682}

view details

arthursonzogni

commit sha b7a876caf70a8124d66f1a112d39c3712b2fa125

[Credentialless]: WPT vs CacheStorage. 2 cases about "omit". On https://github.com/w3c/ServiceWorker/issues/1592#issuecomment-838741939 I mentioned 5 "interesting" cases about `COEP:credentialless` and CacheStorage. All are already tested, except the 4th. This patch introduces two new tests with request.credentials="omit", including the missing one above. R=antoniosartori@chromium.org CC: clamy@chromium.org CC: mkwst@chromium.org CC: lyf@chromium.org Bug: 1175099 Change-Id: If8ea3ebc9efd6622be0d8c4dae7eba1bb28ce3bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2917020 Reviewed-by: Antonio Sartori <antoniosartori@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#886703}

view details

Mattias Buelens

commit sha 7b29ee36cc22bdad06b4f98df73358ca959fe0a7

Streams: tests for readable byte stream fixes Follows https://github.com/whatwg/streams/pull/1123.

view details

Fredrik Söderqvist

commit sha 69032b42bd96f3fd889fef7730ed7ff53fb3e167

Fix wpt/css/css-backgrounds/background-332.html The 'background-size' component of the shorthand is '10em' - which is the same as '10em auto' (not '10em 10em'). Also, the value should be the computed <length> (160px). Thus '160px' will be the shortest computed form. For the 'background-repeat' component, 'round' is equivalent to 'round round' but the former is the shorter form. Fixed: 1184497 Change-Id: I82e9bfbfdf6eac2ca7781d4332e7954ef7cbdb8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2919751 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#886764}

view details

Delan Azabani

commit sha dce98cf58c52db5fb92f2eed697955cf667f1fb9

CSS highlight painting: fix ::selection decoration regression NG’s text-decoration support is currently pretty buggy. One of these bugs is that we make no attempt to paint any decorations on selected text (part of bug 1147859), only the originating text’s decorations. Notice how the line-through (blue) is behind the selected text (grey) in <https://wpt.live/css/css-pseudo/highlight-painting-003.html>: https://bucket.daz.cat/791f25c9b0bbd7e4.png /c/2647046 reordered highlight painting such that the ::selection background is painted over originating text (part of bug 1147859). This worsens the impact of the first bug, making the decorations difficult or impossible to see when text is selected: https://bucket.daz.cat/5e546e5bb1dab511.png This patch makes the minimum changes necessary to fix the regression without reverting /c/2647046. It approximates pre-M90 painting by “lifting” decorations to ::selection overlay when text is selected: https://bucket.daz.cat/ac5cdae75969f321.png One minor side effect of this is that underlines and overlines, which are supposed to paint under text, will also “lift” so they paint over unselected text whenever the user selects text. Splitting decorations so that they can correctly order with both unselected and selected text at the same time is best left to a subsequent patch. Bug: 1209248 Change-Id: Ie7da0e4369e96fd337e0a90bdcd6631dfb6aee05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2902289 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Delan Azabani <dazabani@igalia.com> Cr-Commit-Position: refs/heads/master@{#886768}

view details

Antonio Sartori

commit sha 5158bae204bca78caa1b9b92e94c589bea97a02f

[wpt] Add test for referrer policy of srcdoc This CL adds an assertion checking that modifying referrer policy of a document has no effect on a srcdoc child iframe which was created before. Bug: 1130587 Change-Id: I2a5b08e7a00e59687c28e8f40e97960d3cacf6b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2919810 Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Reviewed-by: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/master@{#886772}

view details

Aaron Krajeski

commit sha ea7318fd06820d1e6ef633793dc69a9829d1a190

Use Dictionary in CanvasFilterOperationResolver Refactor the CanvasFilterOperationResolver to make use of classes already available in the blink/renderer/bindings/core/v8/ directory. Filters attributes are defined here: https://drafts.fxtf.org/filter-effects-1/ Bug: 1169216, 1210394 Change-Id: I00b725b81fa9d2ab14d02eef9d66af4afd14c6c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2910714 Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Cr-Commit-Position: refs/heads/master@{#886779}

view details

Aaron Krajeski

commit sha 9d7eaf14cfd6a6b3855dcc92ea55baa2126f0a68

Add a ref test for canvas component transfer filters Implementing new SVG Canvas filter interface as defined here: https://github.com/fserb/canvas2D/blob/master/spec/filters.md As defined in SVG: https://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement Bug: 1169216 Change-Id: I4241e048f4e66efcf7938e78ab8656f94570c6fe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2911074 Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Reviewed-by: Yi Xu <yiyix@chromium.org> Cr-Commit-Position: refs/heads/master@{#886797}

view details

push time in 8 minutes

push eventWebKit/WebKit

Per Arne Vollan

commit sha aef5bd9e27d33901f93a2100ba05f8737801ae24

[iOS] Sync Accessibility preferences https://bugs.webkit.org/show_bug.cgi?id=226738 <rdar://77922839> Reviewed by Brent Fulgham. Source/WebKit: Only attempt to modify Accessibility preferences if they have changed. * Shared/AccessibilityPreferences.cpp: Replaced. * Shared/AccessibilityPreferences.h: Replaced. * WebProcess/cocoa/WebProcessCocoa.mm: (WebKit::WebProcess::accessibilityPreferencesDidChange): Source/WTF: Enable Per-App Accessibility preferences on iOS. * wtf/PlatformHave.h: Canonical link: https://commits.webkit.org/238777@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@278824 268f45cc-cd09-0410-ab3c-d52691b4dbfc

view details

push time in 11 minutes

issue commenttc39/proposal-regexp-set-notation

IgnoreCase vs. complement vs. nested class

Intuitively I would also expect adding ignoreCase to match more, not less. That's just my personal opinion though.

In the current implementation in V8, iirc, we apply case folding close over for individual \p, which of course means that with inversion we end up excluding more. The solution would be to wait with closing over for case folding after the character class has been fully defined.

markusicu

comment created time in 11 minutes

pull request commentmdn/content

Remove capital in slug of FetchEvent.preloadResponse

<!-- build_hash: 17015e27c657cb42389fb1a7bead9593 date: 2021-06-14 09:28:24.022347 -->

Preview URLs

Flaws

None! 🎉

External URLs

URL: /en-US/docs/Web/API/FetchEvent/preloadResponse Title: FetchEvent.preloadResponse on GitHub

No new external URLs

teoli2003

comment created time in 12 minutes

issue commentmdn/content

API structure conventions: syntax sections for properties?

I propose moving this to the Discussion tracker.

Elchi3

comment created time in 14 minutes

PR opened mdn/content

Remove capital in slug of FetchEvent.preloadResponse

Attributes, properties and methods mustn't start with a capital letter (in the general case).

This was the case, so I'm updating the case.

No redirect is needed, so only 1 file is touched.

This was detected by @foolip in mdn/browser-compat-data#10983

+1 -1

0 comment

1 changed file

pr created time in 15 minutes

issue commentfacebook/react

React 18: react-router@v5 is breaking in the Strict Mode (strict effects)

For example, TikTok has upgraded to React 18 already (twitter.com/Brooooook_lyn/status/1402632529270632456?s=20)

This looks like they're just testing integration, not pushing React 18 to production.

I personally don't see any issue with app devs trying the alpha already. From how I understood it, this isn't generally recommended because most apps use at least one library. So it might be frustrating if you want to try it out, but upstream isn't ready. So right now the goal is to work the problem bottom up so that library maintainers aren't flooded with issues regarding "React 18 compat when?". But that's just from my perspective.

Rather than listing libraries that aren't ready (putting negative pressure on those maintaienrs) we may want to start a list of the libraries that are compatible. Though right now is probably too early.

can reduce other one's time-wasting.

I think there's a mismatch of expectations here. Upgrading to React 18 right now is most likely not the most productive task. Upgrading and facing issues right now should be the expecation so considering it a "waste of time" isn't very constructive. The React working group is actively looking for such issues right now. Idenitfiying these issues is the exact opposite of "wasting time".

Jack-Works

comment created time in 15 minutes

pull request commentnodejs/node

test: use localhost test instead of connecting to remote

CI: https://ci.nodejs.org/job/node-test-pull-request/38622/

AdamMajer

comment created time in 16 minutes

pull request commentnodejs/node

fs: use missing validator

CI: https://ci.nodejs.org/job/node-test-pull-request/38623/

VoltrexMaster

comment created time in 16 minutes

pull request commentmdn/content

Fix Sample link

Yechezkel, thanks for catching this and fixing it, and congrats on landing your first docs change here — welcome aboard 🎉

chderen

comment created time in 17 minutes

pull request commentmdn/content

Fix Sample link

<!-- build_hash: d07103ed5a9f6a8d9d0712ed430a3108 date: 2021-06-14 09:22:08.753532 -->

Preview URLs

Flaws

URL: /en-US/docs/Web/API/File_and_Directory_Entries_API/Introduction Title: Introduction to the File and Directory Entries API on GitHub Flaw count: 8

  • broken_links:
    • No need for the pathname in anchor links if it's the same page
    • No need for the pathname in anchor links if it's the same page
    • Is currently http:// but can become https://
    • Is currently http:// but can become https://
    • Is currently http:// but can become https://
    • and 3 more flaws omitted

External URLs

URL: /en-US/docs/Web/API/File_and_Directory_Entries_API/Introduction Title: Introduction to the File and Directory Entries API on GitHub

No new external URLs

chderen

comment created time in 18 minutes

push eventmdn/content

Hamish Willee

commit sha c4602088f6639d3b151d57638d3759827e95bc32

Page macro: Remove example inclusion in pannernode methods (#5971)

view details

push time in 19 minutes

PR merged mdn/content

Reviewers
Page macro: Remove example inclusion in pannernode methods

This is part of global removal/reduction in Page macro tracked in #3196

This is same as #4401. A bunch of example code now links rather than imports BaseAudioContext.createPanner

+18 -77

1 comment

7 changed files

hamishwillee

pr closed time in 19 minutes

push eventmdn/content

Hamish Willee

commit sha 083cf993d25eaf19e1e24b3fc8867bd34d289f00

Page macro: Replace VRDisplayCapilities example include (#5973)

view details

push time in 19 minutes

PR merged mdn/content

Reviewers
Page macro: Replace VRDisplayCapilities example include

This is part of global removal/reduction in Page macro tracked in #3196

This is same as #4401. A bunch of example code sections now link rather than import example code in VRDisplayCapabilities

+11 -11

1 comment

8 changed files

hamishwillee

pr closed time in 20 minutes

push eventmdn/content

Hamish Willee

commit sha e20620d3da0311f253a50e994effc702c66d8441

Page macro: Replace macro with links to VRDisplay.getframedata() (#5974)

view details

push time in 20 minutes

PR merged mdn/content

Page macro: Replace macro with links to VRDisplay.getframedata()

This is part of global removal/reduction in Page macro tracked in #3196

This is same as #4401. A bunch of example code now links rather than imports VRDisplay.getFrameData()

Note, I did consider moving the example up to VRDisplay and linking to that, but that object already has a different example.

+14 -14

1 comment

12 changed files

hamishwillee

pr closed time in 20 minutes

pull request commentmdn/content

Document what "new Date()" returns if given invalid date string

<!-- build_hash: 906ac7b3fa4c66086b07f4f145a52c1f date: 2021-06-14 09:20:01.716214 -->

Preview URLs

Flaws

None! 🎉

External URLs

URL: /en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/Date Title: Date() constructor on GitHub

sideshowbarker

comment created time in 20 minutes

issue commentnodejs/node

new vm.Script only evaluates cachedData once

even if the same filename is used again

that's weird. filename is aslso the same when you don't specify it (it defaults to 'evalmachine.<anonymous>')

Ilmarinen100

comment created time in 21 minutes

issue commentmdn/content

Issue with "Date() constructor": (short summary here please)

Thanks for raising this — I’ve opened https://github.com/mdn/content/pull/5983 with a fix.

aronbeal

comment created time in 22 minutes

PR opened mdn/content

Document what "new Date()" returns if given invalid date string

Fixes https://github.com/mdn/content/issues/4817

+13 -7

0 comment

1 changed file

pr created time in 22 minutes