I have a Bootstrap navbar that has a breakpoint of 767px.
One particular tester, using Google Chrome does not get the navbar breaking when amending the screen width using Developer Tools. Same Chrome version as everyone else (54.xxxx) who gets the correct behaviour. Instead, it breaks at 691px
Obviously this is a machine setting rather than Google Chrome. What could the setting be (Windows 7)?
Many thanks
This behaviour was due to the zoom ratio on Chrome. The user had it set to 90%
Related
I am using Firefox 50.0. After auto update of Firefox to version 50.0, Firebug has stopped working and attempting to use it is showing an inbuilt Firefox console while inspecting any DOM element.
Is there any patch to use Firebug on Firefox 50.0 version?
Solve The problem by Changing Mozilla Browser Configuration Settings.
Open A Blank Tab
type about:config in address bar then press enter (click on I accept the risk!)
find browser.tabs.remote.autostart
select the option then click the mouse right side
Turn The Option As False
Close the browser for restart browser
open browser again, inspect the element. I hope It Works Properly.
I manage to get Firebug work again, so here is what I done.
Everyone knows that Firebug isn't being developed or maintained any longer because it can't work with e10s, so here is my workaround:
Download Firefox Developer edition so you can allow XPI installation.
firefox-53.0a2.en-US.win64.installer.exe or
firefox-53.0a2.en-US.win32.installer.exe
Run Firefox developer edition after installing and go to the about:config (type in url bar)
Find xpinstall.signatures.required (set to false)
Find browser.tabs.remote.autostart (set all to false: browser.tabs.remote.autostart.1 and browser.tabs.remote.autostart.2)
NOTE: The Multi-process architecture improves the browser's stability, performance and security by separating tasks into processes, you disabling it at own responsibility.
After that you need to restart the browser.
Now you can go at the Firebug repository and install desired version
Here you can find all Firebug installations
I chose latest firebug-2.0b8.xpi and it forking fine.
P.S. You can disable updates for Firefox Developer edition.
Hope it helps.
Head over to Firebug website, you can see following message:
The Firebug extension isn't being developed or maintained any longer. We invite you to use the Firefox built-in DevTools instead.
Also Sebastianz told me,
Firebug is discontinued. The team has split up, the former team leader Jan "Honza" Odvarko is working on the Firefox DevTools now.
As #Makyen said in his answer, Firebug does not work with multiprocess Firefox, so remove Firebug right now and try Firefox DevTools instead, it's not optional (sadly), unless you don't update Firefox :)
Update 1
Take a look # Why got Firebug removed after updating Firefox to version 50?
Update 2
Take a look # my answer here: how to revert firebug to old version
Firebug does not work with multiprocess Firefox
The Firebug site claims that:
Firebug 2.0.18 is compatible with Firefox 30 – 52
However, it also explains that [emphasis mine]:
Firebug 2.0.18 fixes issue 8030. The extension is marked as multi-process (e10s) compatible so, it isn’t blacklisted and users can continue installing it. This way Firebug can help users to easily migrate into built-in Firefox developer tools – in case it’s running in multi-process enabled browser. When opened in a multi-process Firefox, Firebug’s tools cannot be used. Firebug will then only assist the user with migration to Firefox’s built-in tools.
They also direct you to read: Unifying Firebug & Firefox DevTools
That page says that [emphasis mine]:
Firebug 2 doesn’t work in multi-process browsers (i.e. e10s) and converting it is too complex, so it will stop working when e10s is activated in Firefox. You will be able to disable e10s for a while to keep using Firebug 2, but this won’t last forever.
The fact that Firebug does not actually work in multiprocess Firefox will account for different people having different experiences with Firebug working or not working in a particular version of Firefox. Firefox automatically enabling multiprocess mode will depend on multiple factors, including what other add-ons are installed in the profile.
Using Firebug in newer versions of Firefox
Thus, to use Firebug in newer versions of Firefox, you will need to disable Firefox from entering multiprocess mode. This can be done from the about:preferences page (also available from Tools➞Options). This an option which is under the "General" tab as "Enable multi-process Firefox ...". If multiprocess is not available, this option will not be shown. This option can also be changed by adjusting the preference browser.tabs.remote.autostart from about:config. [Note: browser.tabs.remote.autostart.2 and browser.tabs.remote.autostart.1 also appear to be used to indicate default states, thus I suggest using the about:preferences page to change this option.]
You can determine if your Firefox is currently running in multiprocess mode by looking in about:support. The line "Multiprocess Windows" under "Application Basics" will state if multiprocess is enabled or disabled.
Set up profiles explicitly for testing
Personally, I have different profiles set up for each of multiprocess explicitly disabled and multiprocess explicitly enabled (set browser.tabs.remote.force-enable to true), so I can perform testing under both conditions, with the state of multiprocess being enabled/disabled being known in advance.
I had the same problem when I updated Firefox. I was so addicted to firebug but I moved on to Firefox developer edition - https://www.mozilla.org/en-US/firefox/developer/
It also comes with the firebug theme which resembles firebug UI and its efficient.Just install FDE and activate the firebug theme as shown in the image below :
I had the same unexpected surprise when ubuntu updated FFX and suddenly things like the script panel stopped working. Since I was in the middle of working on something with a short deadline, I was not going to have the luxury of learning the firefox developer toolset and desperately needed to get firebug working. The fix that finally worked for me was to set Firefox preferences not to update. Then download v 49.0.2
https://support.mozilla.org/en-US/kb/install-older-version-of-firefox
I also had to tell Ubuntu not to include firefox in it's upgrades.
It looks like firebug will no longer be maintained as a seperate project, so you will want to get familiar w/ the built in dev tools, but hopefully this buys you some time. Worth mentioning (if I'm reading this right, it sounds like it will be integrated into the native tools:
https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/
https://github.com/firebug/firebug.next
Its working. You need to install one more add-on "Firepicker" and restart the Firefox.
https://addons.mozilla.org/en-US/firefox/addon/firepicker/
I managed to resolve this issue by simply downgrading to mozilla old version using this url:
open https://ftp.mozilla.org/pub/firefox/releases/50.0/win64/en-US/
download and run the .exe setup
Go to Settings - > Add Ons
Click on extensions and search for firebug and firepath and then add those extensions
Hope this should resolve the issue. For those using Windows 32 machine can use the url
https://ftp.mozilla.org/pub/firefox/releases/50.0/win32/en-US/
http://toolsqa.com/selenium-webdriver/xpath-helper/
Open a new tab and navigate to any webpage. I have used www.DemoQA.com for demo.
Hit Ctrl-Shift-X (or Command-Shift-X on OS X), or click the XPath Helper button in the toolbar, to open the XPath Helper console.
Hold down Shift as you mouse over elements on the page. The query box will continuously update to show the XPath query for the element below the mouse pointer, and the results box will show the results for the current query.
If desired, edit the XPath query directly in the console. The results box will immediately reflect your changes.
Repeat step (2) to close the console.
I need your help my website is not functioning properly on firefox browser but in edge, chrome and opera and safari it works only firefox is not functioning properly
Firefox Browser
Google Chrome Browser
I would recommend setting up all your projects in Xampp or something similar first before testing it. If you are going to upload to a server you need to replicate the environment locally before you decide whether it is going to work or not. It seems complicated but it is quite simple, you can find out more here. https://www.apachefriends.org/
That said, check your urls, they are not the same for your two different screens, the one is referencing an anchor tag.
I'm using WP Mobile Detector with W3 Total Cache and a responsive layout (media queries), and I have a few issues:
When I view the site locally (localhost) on a Blackberry, it looks good; the zoom/viewport is correct, media queries have trigger correctly etc. However, when I view the live site on the Blackberry, the viewport has zoomed out. In the context of a responsive layout, locally I see two columns, but on live I see all six columns (i.e. the Blackberry thinks it is a full browser - quite annoying!).
I thought I would deactivate W3 Total Cache to see if that was having any effect: yes, it was. When the cache is off, the viewport/zoom is good and all is well. Problem solved? Not quite...
With the cache off, I navigate to the live site and while the sub-pages of the site - e.g. www.SITE.com/about, www.SITE.com/contact - are responding with the mobile theme, when I click a link back to home (or type it into the address bar) - i.e. www.SITE.com/ - I'm no longer delivered the mobile theme, just the normal 'desktop' theme. If I go back to a sub-page I see the mobile theme again. What's going on there then.
When viewed on the Blackberry (for example), if I click the 'View Full Site' link (which triggers a Javascript function to modify the cookie) it doesn't show the full site (i.e. normal theme), it just refreshes and shows the mobile theme. However, when viewed in Firefox on the desktop (via a User Agent Switcher) the link DOES modify the cookie and switches back to the normal desktop theme.
Thoughts/Questions
W3TC does work with WPMD (mobile theme delivers minified JS/CSS), but maybe I haven't configured something correctly. The following two links were very useful and I have implemented the changes suggested:
--- http://snipplr.com/view/47970/wp-mobile-detector--w3-total-cache-integration/
--- http://journal.code4lib.org/articles/6223
Is this a known [Blackberry HotSpot/Internet Browser] issue? I have added the requisite meta tags in the document head to indicate viewport data, and the HandheldFriendly meta data which I understand is mainly for Blackberry purposes. As I said, it looks ok with the cache switched off, excepting the home page issue.
I should say it works nicely in Firefox with the User Agent Switcher extension set to iPhone 3, and I have none of the Blackberry issues.
WPMD works by setting a cookie. This appears to be working, else I wouldn't have seen the mobile theme at all.
Does the Blackberry have a problem with the Javscript function? Not easy to tell from the phone itself - might need to drop in a JS error monitor (I was looking at one the other day).
Who'd have thought mobile dev would be so tricky!
UPDATE 1
It's a few weeks since first posting, and I will soon be following Joshua and Frederick's advice to uninstall and then reinstall the [latest version of] W3TC and I'll post my results.
I found that different browsers (both desktop and mobile) treat javascript redirect statements differently. For example:
setTimeout(function(){window.location.reload();},10)
window.location.reload();
location.reload();
The three lines above effectively perform the same action (slightly different implementations, depending on your needs), but I had varying success across browsers using each one - Chrome worked with one, Firefox another, etc.. Unfortunately, I still could not get the Blackberry browser to perform a proper automatic refresh via Javascript.
What else...so, switching between desktop and mobile using a desktop PC/browser has proven interesting. Let's say we're on the desktop version, and we switch to the mobile version of the page. We're OK so far, but then we switch back to the desktop version of the page. Still OK, but if we quickly click a link on the desktop page to go to another [desktop] page then we may find ourselves looking at the mobile version instead of the desktop version.
So, what happened there? As the page was still loading when we clicked another link, did we interrupt something? Presumably not, as the cookie would have been set and sent in the previous request from the mobile version of the page to say, e.g., "show-desktop-version = true". If we do hit F5 or the browser's 'Refresh' button (or, in fact, a link to any other page) then we do see the correct mobile or desktop version (respectively).
Another interesting thing: say we're on our mobile version (using desktop browser), and we're looking at site.com/mypage, and on the page is a link to 'View Full Site' (VFS). We click VFS once and it refreshes but we're still seeing the mobile version. So we click again - same result. So we click again, and again, and again, and again, and - oh, OK this time it switched to the full site. This cycle/process seems to occur once, and then not for a while, and then happens again.
UPDATE 2
Regarding the mobile-desktop theme switching problems, please disregard my notes in 'Update 1'. One of my switcher links (from desktop theme to mobile), e.g....
View Mobile Site
...was using the query parameter (as you can see). I had used this technique to test whether a mobile browser was preventing a proper refresh as the link pointed to the same/current URL. The switcher link should have actually looked like this,
View Mobile Site
...with just a hash to allow the link to be clickable, while allowing the Javascript function to do its magic (update cookie, reload page).
Problem resolved.
(W3TC + WPMD compatibility still an issue for me - will post updates).
I am the developer of the WP Mobile Detector.
The issues you describe are exactly what happens when the W3 Total Cache is installed. For whatever reason, sometimes it is necessary to deactivate and delete the W3 Total Cache.
Two customers that I can remember reported issues even when the W3 Total Cache was disabled. Once it was removed, it fixed the problem. They then re-uploaded W3 Total Cache, made the changes at the link you posted, and seemed to be fine.
For whatever reason these issues seem to be more prevelant with newer versions of the W3 Total Cache. I need to get with Frederick (the creator of W3 Total Cache) and make sure the plugins play nice together.
Make sure to clear your cache on the BlackBerry device as well.
Without evaluating the plugin there are some things to consider here. First W3TC attempts by default to set a cookie to properly determine which page cache to use for user agent groups for smartphones and less-smart phones; it keeps unique caches for each because of the popularity of mobile theme plugins prior to popularity of responsive web design and progressive enhancement.
The user agent groups can be disabled or used to redirect visitors to another page or theme. The next release also removes the need for the cookie when user agent groups are set. A future release will also allow cookies to be used to unique cache user requests as well.
I'm having troubles testing a StageVideo file locally. The HTML file that contains the swf loads perfectly in Chrome & FireFox, but when I go to open it in Internet Explorer 9 nothing happens (it just shows a white screen).
I've added the permissions for the location to the 'Global Security Settings' tab of the Flash settings manager (on the Macromedia website). I've also checked in the IE9 settings to make sure that it allows GPU rendering.
Has anyone encountered anything similar or have any suggestions as to why it might be blocked in IE9?
Thanks in advance.
My gut feeling is that you don't have the latest Flash Player for IE, but do have it for Chrome/FF since they're 2 different versions. The swf probably doesn't even load up because of the Flash Player requirement.
I'm looking into chrome frame and I'm wondering how it works.... http://scriptsrc.net shows that it's a javascript that can be embedded on the page....
http://code.google.com/chrome/chromeframe/ shows it as an install file... does the JS prompt for an installation or something?
Google chrome frame is a plugin (think Adobe Flash) for Internet Explorer, that replaces core modules of IE (unlike Flash), like layout/rendering and javascript. But the UI remains. Then there is some javascript that can detect if this is real IE or IE+Chrome, and also offer an install option to the user. Also there is a HTTP-header and a meta-tag that are required to switch IE to chrome mode, when available.
The JavaScript is to detect it and enable it if it's there. (scriptsrc is just giving you the link to the file, which is on the Google CDN.) The end user does have to do a one-time install of it, it's a plug-in (like Flash or Java). Quoting from this page in the Google documentation:
In Internet Explorer, check() determines if Chrome Frame is installed. If not, the user is prompted to install it.