I try to open a mdc-dialog inside a mdc-dialog. When closing the second dialog, material-components-web closes both dialogs, instead of returning back to the underlying dialog (first dialog). See the example on codepen.io.
Is that a bug or do I missed something?
After analysing the source code of mdc-dialog I'm pretty sure, that it is a bug. Just opened a new bug on github for material-components-web
Related
This annoying window when you go to definition is impossible to disable and has been a blemish on an otherwise first rate code editor.
For some reason it picks up .d.ts files and I get the window even when there is only one definiton. I would love to remove this feature but it does not seem possible.
Below is a screen shot of it picking up a definition and for some reason a react index.d.ts file. So annoying, I can never go to the definition, I've got to click about until the preview window decides it wants to close:
What finally cured it for me was:
"editor.gotoLocation.multiple": "goto"
Is there any way to completely remove this message popup or move it to somewhere?
I already know why this message comes, but I do not want to disturb my activity with annoying info popup.
When it pops up it hides the document tab, so I have to close it every single time. (I do not want to know how to fix this particular error message, this screenshot is just an example.)
It's very annoying and I've searched around for a way to remove it, but the answers keep saying how to fix that particular error and not how to hide the popup itself.
Press ESC.
I agree that this is really annoying. VS Code is all about high-speed workflow and not having to interact with anything except your code via keyboard. Everything has key chords, e.g. CTRL-P and CTRL-SHIFT-P. So having to stop what I'm doing, go to the mouse, and dismiss this popup, whenever a background task feels like completing (and not even really then, because the popup actually appears some short time later) just so I can get visual confirmation of which file I'm currently coding in, to refocus my work after being distracted by the same popup, is really awkward. They are in a stupid location and don't even fade away after time like well-behaved toasts.
That said, I think that's really two parts; the distraction, and relatively high workflow cost to dismiss.
It helped me a lot to learn that it can be dismissed quickly and easily with the ESC key. The other half the problem I still haven't solved, but hope that helps you.
In the screenshot it shows trying to validate PHP.
In a VS Code window select File > Preferences > User Settings
An editor will open on the left called Default Settings and on the right with a file called settings.json
In the right side editor you can add settings that will override those found in the left-hand-side one.
Between the braces type:
// Whether php validation is enabled or not.
"php.validate.enable": false,
Then save the document.
VS Code will no longer attempt to validate PHP files.
You can override any of the defaults using this method.
You can use the same technique for each Workspace (or project folder) using File > Preferences > Workspace Settings
You can't disable the alert bar in general as VS Code needs to tell you things and doesn't (thankfully) use modal dialogs to communicate.
Go to File > preferences > settings
Then add this to your user settings
"editor.parameterHints": false
You may want to try adding the line
"extensions.ignoreRecommendations": true
to your VS Code settings file (which you can easily reach with the keystroke (CMD + ,) on a Mac OS X or macOS system.)
Solution: User Preferences > change "editor.parameterHints": true to "editor.parameterHints": false
This will at least remove the obstructive boxes that appear above the cursor.
Firefox has a feature in debugger that lists events for nodes - here's a help article for it.
For unclear reasons, I can't find a way to remove any of those listeners. How do I do that?
It seems that right-clicking the element in the inspector, choosing "Edit as HTML" and modifying the html code (even as slighltly as adding a space after the code) makes the listener go away
The same feature is there from the inspector in Chrome, but as you say not in (newish) DevTools in Firefox.
Before DevTools, it was there in Firebug (screenshot), but the issue to port it across has been open for 3 years.
The only workaround I've discovered, is to disable JavaScript altogether. You can do that in the "Debugger" tab, in the debugger settings to the right. Unfortunately that causes the page reload.
First introduction to chrome apps. I'm trying to get some sort of workflow down. I've enabled the checkbox to collect errors, but can not seem to clear them between executions of the app. I assumed closing the app them re launching it would do the trick. The only thing that works right now is deleting the app then reloading the package.
To clear the list of errors at "Collect errors":
Toggle the "Developer mode" checkbox (disable, then re-enable).
Click on the Reload link (reload extension/app).
Refreshing the page instead of reloading the app/extension also works.
Using the 39.0.2171.95 64-bit Chromium all I need to do is toggle the Developer mode
I think the solution suggested by Rob does not work anymore for recent versions of Chrome.
You clear the errors by following the steps below.
Go to chrome://extensions
If it's not enabled, enable the Developer mode, see below.
Click on the Errors button (in red in the picture below) on the extension.
Now you can either delete each single error by clicking on the trashbin icon next to it, or you can just clear all errors by clicking on the Clear all button depicted below.
This happens only on Linux. I have a ComboViewer where some elements trigger a dialog to appear. What happens (I debugged this) is when combo box is expanded ISelectionChangedListener.selectionChanged is fired. This causes first element of the viewer to be selected and dialog launched. This occurs in a two page wizard, so once this happens and I go to previous page and then come back to the one with the viewer I don't see selectionChanged firing upon combo box expansion.
On Windows I don't see this problem - selectionChanged only occurs when element is explicitly selected from the combo box.
Does anybody know if this is a known problem and is there fix for it? I understand that my case is somewhat unique.
thanks,
Alex
Sounds like a bug to me. I understand you can search the Eclipse bug database, this might be a repeat.