I am using
"#fluentui/react-components": "^9.7.1",
error: Modalizer i9 must have either aria-label or aria-labelledby
I am getting this warning and I have checked there is no error but when I click on the trigger, It shows this warning in the console and popover dosent open
Maybe it's because Fluent UI v9 does not support React v18 yet, see this GitHub issue, which causes some issues with React's StrictMode.
You can solve the issue by disabling Strict Mode.
Related
Each Time I'm using this console I'm struggeling with my mouse to click on the editable line.
So two question :
Is there a way of enlarging this line so it easier to click on it ?
Is there a command to navigate to it ?
The only way to enlarge it is to create a custom theme for DevTools, enable the experiment for using custom themes, and then installing your extension. That way you can get custom CSS into the top-level DevTools scope to modify things.
You may open a bug report on the chromium issue tracker against the DevTools so the team can assess the UX to see if there is anything they should modify internally.
I am working on a UWP component that relies on Window.Current.Activated event to check whether the window is focused or not. On some apps using this component the technique does not work. Anyone got any ideas on how Window.Current.Activated might not be raised?
I am a web developer. One of the js Library we use in our web application is knockout js. To make it easier to debug we use Knockoutjs context debugger plugin. However when ever we inspect any element and trying to view knockout objects on Knockout Context tab in Chrome inspector, the browser is hanging and then crashing.
At that point of time when I open the Task manager the chorme.exe is taking high memory than any application.
Steps to Reproduce this issue:
1. Install knockout context debugger plugin for chrome browser.
2. Open any single page web application which have at least 25 view models which are worked together in the application in chrome.
3. Open inspector and try to inspect any element which has knockout bindings.
The browser will be going into unresponsive, then hangs and eventually crashes
How to resolve this problem with out uninstalling Knockout context debugger plugin?
Edit Based on comments:
It is also happening in my colleagues machine as well. They are also facing this problem
The browser hangs for various reasons. Mostly due to below reasons. Some of them are
Serialization of DOM elements, Circular reference etc..
The most common root cause for this problem is you might enable serialize option in knockout context debugger options. Below is the resolution for that problem
Go to Chrome settiongs--> Extensions--> Knockout Context debugger--> Options
Deselect Serialize (provides the best visualization) checkbox if it is already selected
Below discussion thread discusses in detail about various reasons behind the hanging of browser
Constantly hangs the browser
I am experiencing a weird behavior of the polymer designer tool. When I click on the code/designer toggle button it switches to the code. Then when I switch back to the design it is gone. The Tree also only shows the default my-element element. Am I the only one who is experiencing such behavior? Is there a solution?
PS: I'm using chrome.
If you can't wait for the fix on the Polymer site, then you can clone the designer code from GitHub https://github.com/Polymer/designer and you'll find that the bug doesn't exist in that code.
When interacting with a RichEditableText component especially when i click copy i get the following error message:
Error #2191: The Clipboard.generalClipboard object may only be written to as the result of user interaction, for example by a mouse click or button press.
The above error is reproducable sometimes in mozilla firefox browser. It is working fine in IE.
Can any one tell me how to handle that error in flex.
from google search i found that it is a bug http://tech.dir.groups.yahoo.com/group/flexcoders/message/159638.