Just installed TOSCA and using the free trial version.
I do not know why when I do desktop scan for my internet explorer browser, it doesn't scan/recognize any of the properties. (Please see picture)
My resolution and browser is set to 100% already as recommended.
Anyone know how to fix this issue?
I think I know what went wrong - I tried this with my copy and I get the exact same result if I choose UIA to scan the window. Be sure that you use Html - you can select that when you are in the "Select Application" dialog, right after you start the scan.
When you right click the Internet Explorer there, you get a drop down where you can select this:
Related
I'm building my first application using CSS Grids.
Using Firefox's DevTools, I'm able to to highlight the Grid's tracks by clicking "# grid" next to an element in the "Rules" pane :
But when I click the "Layout" pane, it always shows "CSS Grid is not in use on this page":
Why is that?
(I'm using the latest Firefox version available today, "62.0.2")
UPDATE: Here's an example project.
UPDATE 2: It does work when I create a new, fresh, profile! But it doesn't work with my current profile, even when I start in safe mode, with all add-ons disabled... I guess I'll customize a new profile!
I agree with you indeed this is a bug in Firefox, I'm using the latest version of developer edition 85.0b9, I faced the same issue. You can clearly see, I've display as Grid still it says CSS Grid not in use on this page.
Issue - It happens when you open it in the default or the 1st Tab, it's not setting some tab-value there. The bug is still not fixed by Bugzilla's dev team, open from past 2 years. Let's hope they fix in future.
Issue Link - https://bugzilla.mozilla.org/show_bug.cgi?id=1492370
Solution - Just duplicate your tab, it'll work like a charm.
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
I'm a mid level website designer and manager for clients sites and I know just enough HTML/CSS to be dangerous. I use the Chrome developer tools to see where I can make CSS changes primarily.
Now for some reason, the debugging tool pauses no matter what I do. I've turned off the pause button, but it makes no difference. Has anyone else had this issue? Do I have a virus or something?
I'm trying to make CSS changes to a Wordpress login page and I can't even get it to react to my changes so I can see what I like.
Thanks in advance for any help. Here is my ugly login page that I need to fix:
http://tracoutdoor.com/wp-login.php
It sounds like your debugger may be set to break on exceptions automatically. If you open the dev tools and click the Sources tab and look at the right hand menu, ensure both the Breakpoints and Exceptions icons are greyed out (not blue) like below:
Also ensure there are no breakpoints set in the Breakpoints section.
Every time I start up a new instance of IE8 32bit, Developer Tools opens automatically. How to disable that and keep F12 functional?
I have tried searching for and deleting all registry keys named IEDevTools (including under HKCU, HKLM, 64bit and 32bit registry). I have also tried adding a DWORD named Disabled, valued 1, at the single location, under HKCU, that gets recreated by IE start-up.
None of that helped. This is a Windows 7 64bit system that has seen multiple up- and downgrades between IE8 and IE9, and also has Chrome and Firefox. (I have seen interaction between Chrome settings and IE settings before, but I can hardly imagine one here.)
People who just want to put F12 to another use, which is not my case, please find your help here.
Well, in my case the following procedure did the trick:
Pin the developer tools window by pressing the small button in the top right corner of the window.
Close the developer tools by clicking on the close button in the top right corner of the docked tools zone.
Now, when you open a new instance / a new tab of IE8, the tools don't come up anymore. It seems that they keep opening when you close an instance of IE8 with the tools active and unpinned (on a separate window).
Hope this works.
I did not figure out the cause, but this is how I got over this in case anyone wonders: IE8 64bit works on the same system without a problem.
(In a next step I had to move on to IE9 because IE8 64bit is not compatible with SharePoint. Yet another step will follow after the last few IE only apps that I still need to use die out.)