[docs] Fix 301 to chromium

oliviertassinari · Sep 18, 2024 · 6e82a16 · 6e82a16
1 parent a7cd830
commit 6e82a16
Show file tree

Hide file tree

Showing 11 changed files with 10 additions and 14 deletions.
diff --git a/docs/data/joy/components/autocomplete/autocomplete.md b/docs/data/joy/components/autocomplete/autocomplete.md
@@ -318,7 +318,7 @@ If you would like to prevent the default key handler behavior, you can set the e
 ### autocomplete/autofill
 
 By default, the component disables the input **autocomplete** feature (remembering what the user has typed for a given field in a previous session) with the `autoComplete="off"` attribute.
-Google Chrome does not currently support this attribute setting ([Issue 587466](https://bugs.chromium.org/p/chromium/issues/detail?id=587466)).
+Google Chrome does not currently support this attribute setting ([Issue 41239842](https://issues.chromium.org/issues/41239842)).
 A possible workaround is to remove the `id` to have the component generate a random one.
 
 In addition to remembering past entered values, the browser might also propose **autofill** suggestions (saved login, address, or payment details).

diff --git a/docs/data/material/components/autocomplete/autocomplete.md b/docs/data/material/components/autocomplete/autocomplete.md
@@ -378,7 +378,7 @@ Browsers have heuristics to help the user fill in form inputs.
 However, this can harm the UX of the component.
 
 By default, the component disables the input **autocomplete** feature (remembering what the user has typed for a given field in a previous session) with the `autoComplete="off"` attribute.
-Google Chrome does not currently support this attribute setting ([Issue 587466](https://bugs.chromium.org/p/chromium/issues/detail?id=587466)).
+Google Chrome does not currently support this attribute setting ([Issue 41239842](https://issues.chromium.org/issues/41239842)).
 A possible workaround is to remove the `id` to have the component generate a random one.
 
 In addition to remembering past entered values, the browser might also propose **autofill** suggestions (saved login, address, or payment details).

diff --git a/docs/data/material/components/menus/menus.md b/docs/data/material/components/menus/menus.md
@@ -90,7 +90,7 @@ If the height of a menu prevents all menu items from being displayed, the menu c
 
 ## Limitations
 
-There is [a flexbox bug](https://bugs.chromium.org/p/chromium/issues/detail?id=327437) that prevents `text-overflow: ellipsis` from working in a flexbox layout.
+There is [a flexbox bug](https://issues.chromium.org/issues/40344463) that prevents `text-overflow: ellipsis` from working in a flexbox layout.
 You can use the `Typography` component with `noWrap` to workaround this issue:
 
 {{"demo": "TypographyMenu.js", "bg": true}}

diff --git a/docs/data/material/components/slider/slider.md b/docs/data/material/components/slider/slider.md
@@ -100,10 +100,10 @@ You can learn more about this in the [overrides documentation page](/material-ui
 
 {{"demo": "VerticalSlider.js"}}
 
-**WARNING**: Chrome, Safari and newer Edge versions that is any browser based on WebKit exposes `<Slider orientation="vertical" />` as horizontal ([chromium issue #1158217](https://bugs.chromium.org/p/chromium/issues/detail?id=1158217)).
+**WARNING**: Chrome, Safari and newer Edge versions that is any browser based on WebKit exposes `<Slider orientation="vertical" />` as horizontal ([chromium issue #40736841](https://issues.chromium.org/issues/40736841)).
 By applying `-webkit-appearance: slider-vertical;` the slider is exposed as vertical.
 
-However, by applying `-webkit-appearance: slider-vertical;` keyboard navigation for horizontal keys (<kbd class="key">Arrow Left</kbd>, <kbd class="key">Arrow Right</kbd>) is reversed ([chromium issue #1162640](https://bugs.chromium.org/p/chromium/issues/detail?id=1162640)).
+However, by applying `-webkit-appearance: slider-vertical;` keyboard navigation for horizontal keys (<kbd class="key">Arrow Left</kbd>, <kbd class="key">Arrow Right</kbd>) is reversed ([chromium issue #40739626](https://issues.chromium.org/issues/40739626)).
 Usually, up and right should increase and left and down should decrease the value.
 If you apply `-webkit-appearance` you could prevent keyboard navigation for horizontal arrow keys for a truly vertical slider.
 This might be less confusing to users compared to a change in direction.

diff --git a/packages-internal/test-utils/src/focusVisible.ts b/packages-internal/test-utils/src/focusVisible.ts
@@ -19,7 +19,7 @@ export function simulateKeyboardDevice() {
 }
 
 /**
- * See https://bugs.chromium.org/p/chromium/issues/detail?id=1127875 for more details.
+ * See https://issues.chromium.org/issues/40719291 for more details.
  */
 export function programmaticFocusTriggersFocusVisible(): boolean {
   try {

diff --git a/packages/mui-base/src/FocusTrap/FocusTrap.tsx b/packages/mui-base/src/FocusTrap/FocusTrap.tsx
@@ -38,7 +38,7 @@ function getTabIndex(node: HTMLElement): number {
   }
 
   // Browsers do not return `tabIndex` correctly for contentEditable nodes;
-  // https://bugs.chromium.org/p/chromium/issues/detail?id=661108&q=contenteditable%20tabindex&can=2
+  // https://issues.chromium.org/issues/41283952
   // so if they don't have a tabindex attribute specifically set, assume it's 0.
   // in Chrome, <details/>, <audio controls/> and <video controls/> elements get a default
   //  `tabIndex` of -1 when the 'tabindex' attribute isn't specified in the DOM,

diff --git a/packages/mui-base/src/Slider/Slider.test.tsx b/packages/mui-base/src/Slider/Slider.test.tsx
@@ -134,7 +134,7 @@ describe('<Slider />', () => {
       expect(slider).to.have.property('tagName', 'INPUT');
       expect(slider).to.have.property('type', 'range');
       // Only relevant if we implement `[role="slider"]` with `input[type="range"]`
-      // We're not setting this by default because it changes horizontal keyboard navigation in WebKit: https://bugs.chromium.org/p/chromium/issues/detail?id=1162640
+      // We're not setting this by default because it changes horizontal keyboard navigation in WebKit: https://issues.chromium.org/issues/40739626
       expect(slider).not.toHaveComputedStyle({ webkitAppearance: 'slider-vertical' });
     });
   });

diff --git a/packages/mui-codemod/src/v6.0.0/styled/test-cases/ObjectMap.actual.js b/packages/mui-codemod/src/v6.0.0/styled/test-cases/ObjectMap.actual.js
@@ -2,8 +2,6 @@ const IconRoot = styled('span')(({ theme, ownerState }) => ({
   userSelect: 'none',
   width: '1em',
   height: '1em',
-  // Chrome fix for https://bugs.chromium.org/p/chromium/issues/detail?id=820541
-  // To remove at some point.
   overflow: 'hidden',
   display: 'inline-block', // allow overflow hidden to take action
   textAlign: 'center', // support non-square icon

diff --git a/packages/mui-codemod/src/v6.0.0/styled/test-cases/ObjectMap.expected.js b/packages/mui-codemod/src/v6.0.0/styled/test-cases/ObjectMap.expected.js
@@ -4,8 +4,6 @@ const IconRoot = styled('span')(({
   userSelect: 'none',
   width: '1em',
   height: '1em',
-  // Chrome fix for https://bugs.chromium.org/p/chromium/issues/detail?id=820541
-  // To remove at some point.
   overflow: 'hidden',
   // allow overflow hidden to take action
   display: 'inline-block',

diff --git a/packages/mui-material/src/Icon/Icon.js b/packages/mui-material/src/Icon/Icon.js
@@ -41,7 +41,7 @@ const IconRoot = styled('span', {
     userSelect: 'none',
     width: '1em',
     height: '1em',
-    // Chrome fix for https://bugs.chromium.org/p/chromium/issues/detail?id=820541
+    // Chrome fix for https://issues.chromium.org/issues/41375697
     // To remove at some point.
     overflow: 'hidden',
     display: 'inline-block', // allow overflow hidden to take action

diff --git a/packages/mui-material/src/Unstable_TrapFocus/FocusTrap.tsx b/packages/mui-material/src/Unstable_TrapFocus/FocusTrap.tsx
@@ -38,7 +38,7 @@ function getTabIndex(node: HTMLElement): number {
   }
 
   // Browsers do not return `tabIndex` correctly for contentEditable nodes;
-  // https://bugs.chromium.org/p/chromium/issues/detail?id=661108&q=contenteditable%20tabindex&can=2
+  // https://issues.chromium.org/issues/41283952
   // so if they don't have a tabindex attribute specifically set, assume it's 0.
   // in Chrome, <details/>, <audio controls/> and <video controls/> elements get a default
   //  `tabIndex` of -1 when the 'tabindex' attribute isn't specified in the DOM,