Fiddler is a great tool.
However something that drives me crazy is the fact that they have several options on the toolbar, but the most important one, the 'Capture Traffic' toggle is only available from the menu.
I know that you can press F12. However when I am in the middle of development, I can't remember if I turned it back on, or its still off. There is nothing to show you if the 'Capture Traffic' toggle is on or off, without looking at the menu.
I have tried looking online, and here at SO for anything on how to modify the toolbar to add this feature, but I did not find anything.
This is a minor problem, but if someone knows how to add this to the Fiddler toolbar, that would be great.
I'm not sure which version of Fiddler you are using, but in v4.4.5.1 there is a useful button in the status bar:
You can click on it to toggle capturing on or off (and if it is not visible then Fiddler is not capturing:)).
Related
I can't preview my Google Optimize experience. Google optimize throws below error:
This happens to me quite often too. The suggestion Google gives is wrong. Clearing cookies and restarting the browser does not fix it. Sometimes rebooting does, but that's a huge disruption.
What I found to work pretty reliably is to end the preview (dropdown), then click the EDIT button to go to the editor. Come back to the setup page, then try Debug again. Debugger should work again.
This is how it worked for me:
In Chrome go to Clear Browsing Data (chrome://settings/clearBrowserData).
Make sure you select checkboxes Cookies and Cached images and files.
Submit the form by hitting the button "Clear data".
Go to preview experience.
For me it started working when I gave the Google Optimize plugin access to all pages (not just the page running the experience).
I think I've found a fix for this. Go to the top right corner of chrome (the three dots) Settings > Privacy & Security > Cookies & other data > and add the url in the bottom section called "sites that can always use cookies"
Example
There can be multiple reasons.
Most obvious: enabled cookies like mentioned by others. should help
If it does not work even when cookies are enabled and you have restarted the browser then more chances are that the issue is in the Experience/Test that you are trying to preview. This can be due to:
A preview is already running in another tab. Turn off preview
2.You have set the experience to run on certain URL patterns and you are trying to preview on a page that does not qualify the criteria.
You have set some Audience rules which are not being met fully. For example: You have set the Audience Device type to mobile and you are trying to preview on a Desktop. Although Optimize will load the preview in a mobile mode but it will not be able to run the experience properly.
In my case the issue was due to wrong device type. I hope it helps.
It's also possible to get this "Unable to preview experience. Please make sure to enable cookies and restart the browser" error message if the content you're trying to modify doesn't exist when Optimize tries to modify it.
I had Optimize set to modify on page load, but the page I was working with was a form, where the text I wanted to modify didn't exist until I clicked through to the second step of the form (still on the same URL).
I was able to just run the study instead on another similar page that had all the text loaded at the start. I'd guess that setting Optimize to trigger from a custom event triggered upon loading the second step of the form instead of "on page load" would also have resolved the issue.
If you are using chrome then:
Click the context menu in the browser toolbar to the right of the
address bar.
Choose Settings.
Select/Search the "Security and Privacy" section.
Choose "Cookies and Other Site Data" Ensure that "Allow all cookies" is selected.
I'm writing a Firefox (web)extension. I have a browser_action in my manifest.json, with a default_popup. I want my extension to be accessible by all users, including those with vision impairment.
So I'd like to, as I change and develop things, test what it's like to (for example) interact with this feature, using only the keyboard. How do I do this? How do I focus and thus "click" the toolbar button, without a mouse?
Ideally, without actually running special screen reader software every time.
So I'd like to, as I change and develop things, test what it's like to
(for example) interact with this feature, using only the keyboard. How
do I do this? How do I focus and thus "click" the toolbar button,
without a mouse?
You can use commands to set a keyboard shortcut.
_execute_browser_action: works like a click on the extension's browser action
You may also add commands.update() (Firefox 60+) API to let users change that keyboard shortcut.
Thanks for considering accessibility. Just to clarify, because I don't think you meant this, but you can do keyboard testing without a screen reader. Just don't use your mouse :-) Seriously.
In my current firefox, I have an address bar, the search field, then a bunch of plugins on a toolbar.
On a PC (should be similar for a Mac, but Cmd instead of Ctrl):
I can move my keyboard focus to the address bar with alt+d or ctrl+L (cmd+L)
I can move my keyboard focus to the search field with ctrl+k (cmd+k)
Interestingly enough, I could not get my focus on the toolbar. I could have sworn I could tab from the address field, to the search field, to the toolbar, but it's not working now.
If you can get your focus there, then you should be able to use the left/right arrows to move between tools and then space/enter to select the tool.
If you want to play with a screen reader, NVDA is free.
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.
Can any one tell how to disable focus to a browser.
Hi i am currently working in .net application and i need to disable the tab focus to browser objects such as toolbars,address bar, since the user will not be using these components often
Thank you
Please don't do this, it breaks what the user expects a webpage to do. Messing with the fundamental behavior breaks several things:
My tab button and where I expect it to go
Screen readers for the disabled
Trust in your application
In some cases, you need to ask why? before asking how?, this is one of those. Anything that behaves differently from the other 99.9999% of the web is broken in the eyes of your user.
Well, I agree with Nick Craver. If you have to disable due to some crap requirements, then try opening a new window without toolbar, editable address bar etc and load the page inside the newly opened window.
customers does not want to allow user to use back or forward button. Just a clean page without commandbar and toolbar, same for FF an IE.
Disabling them is not an option as now.
You cannot change that kind of thing in a existing window -- the only way you can make those disappear is by opening a popup, specifying they should not appear in that popup when it's being opened.
Still, note that you should not try to disable those buttons nor have them disappear : your application should work fine with them, handle their actions -- after all, it's one of the few things users have understood in browsers...
And as a user, this is disturbing and annoying :
I don't like popup windows -- and I'm not the only one who doesn't
I don't like when a website tryies to take control over my browser
It will not always work anyway.
And, as a sidenote : even if the back/forward buttons are not displayed, users can still use Ctrl+left/right or some kind of equivalent !
I know this is not easy, but a part of your work as a web-developper is to explain your clients how Internet and web-applications work... not the same way as desktop applications !
If you can force your users into IE (can't believe I'm suggesting use of IE!) you can do this trick. Try running this from the command line
"C:\Program Files\Internet Explorer\iexplore.exe" -k
This will force IE into kiosk (or full screen mode), similar to pressing F11 when in a usual browser session.
PS. I agree with the other answers suggesting this should be discouraged but there are instances (such as when the end user really can't be trusted) that this is a good solution.
No, there's no other way.
However, this is extremely annoying behavior and should be greatly discouraged. This isn't a code issue to solve...this is behavior that shouldn't be implemented at all.
My opinion here, you have a client problem not a code problem. Whatever standard is the expectation, and the user has the expectation of having their back/forward buttons, break that and you break their experience.
Ever see a Windows application that removes the taskbar? That's the equivalent...
I don't think there is a reasonable way to disable the behavior. You may get rid of the buttons in various ways, but the behavior is still there (through keyboard commands, popup menus and so on).
The only reasonable way is to make your web application follow web semantics, and make the client realize this.
many web based ERP (for example) does not tolerate people using navigation buttons. BUT these web applications handle the fact people use these buttons and do not crash. That's what you should do. If each time people use the back button, they get an error message, they will quickly stop using it.
The solution that used to work in IE was adding a startup script with one line:
location.forward();