The most recent version of Firefox has messed up our internal wiki layout so that the left bar menus are displayed below the content on all pages now.
I've tried using multiple resolutions and window sizes and the problem persists so that doesn't appear to be the issue.
There are no problems with Chrome or IE however.
A screenshot of the problem is attached here for you to see.
You're using an old MediaWiki version. It does UA sniffing and sends different code to different browsers, relying on bugs in some of the browsers to make the code sent to them render correctly.
Firefox 9 removed a nonstandard property that only Gecko used to implement. MediaWiki was using that property to decide that the rendering engine was Gecko. With it gone, MediaWiki now decides that you're using kthml and sends CSS rules tailored to khtml bugs... but Gecko happens to not have those bugs. So the rendering ends up wrong.
Your options are to either update to MediaWiki 1.16 or newer (which you should do anyway, because your version is not getting security fixes anymore!) or wait for Firefox 10 to come out, because chances are that will restore the nonstandard property because too many sites were sniffing for it.
See also https://bugzilla.mozilla.org/show_bug.cgi?id=683151 and https://bugzilla.wikimedia.org/show_bug.cgi?id=31807 for more info.
Related
I'm using a Display Image Item with settings section set to 'BLOB Column returned by SQL statement'.
It shows the image (are big sized) without problems in Chrome, Edge or firefox but on IE it only shows a little black square with an X inside.
Any idea how to fix it?
Support for IE is deprecated since version 20.2, and even before there were features that did not work properly. My advice: don't use IE with Apex, if you can, use always other browsers which are properly supported and work without issues.
Display images might be one of those issues. Starting with Apex 18 this might be due to a problem with IE11 when using the X-Content-Type-Options:nosniff response HTTP header. The images from the display image items are not displayed correctly in IE11 because Apex is not able to define the correct mimetype.
This is reproducible in the case of BLOB Column Return by SQL Statement, which is exactly your case. You can confirm it using the console debug mode.
Notes
6.1.4 Support for Internet Explorer 11: Deprecated Support for Internet Explorer (IE) 11 is deprecated.
Starting with release 20.2, only the current and prior major release
of Microsoft Edge along with Google Chrome, Mozilla Firefox, Apple
Safari will be supported.
Deprecated means you can still use it, but support will ultimately be removed for it. Also as Microsoft has removed IE as its standard browser, replacing it by Edge, it is likely you will always have unexpected behaviour in this browser.
We all know that for security reasons and compatibility with legacy applications, many companies still use IE in order for those applications to work properly. However, using it with Oracle Apex is always a bad idea.
Since last few updates of Firefox our beloved Firebug is integrated into the Firefox Developer Tools and a lot of people including me don't like what happened to Firebug.
The built-in developer tools have a very ugly menu system and messed up usability.
So, what are the alternatives to the Firefox Developer Tools? Is there a tool with the same usability as Firebug?
Alternatives are:
Turn off multi-process Firefox. (Though that's only a temporary solution and doesn't bring back all functionality of Firebug. E.g. the Script panel is broken in current versions of Firefox.)
Install an old version of Firefox where Firebug still works and disable updates. (Also only a temporary solution, because you'll miss (security) bug fixes and new features.)
Wait until the gaps between Firebug and the Firefox DevTools are fixed. (Or even help them fixing them.)
Switch to another browser and use its developer tools.
Rework Firebug to make it compatible with multi-process Firefox (which is the main reason for the integration into the DevTools). Update: Starting with Firefox 57 only WebExtensions will be supported, meaning extensions work cross-browser and are more secure, but they also have limited APIs. So, a reworked Firebug would not have all the features the original Firebug had.
Following Sebastian's advice I've downloaded old Firefox portable v47 from here:
https://sourceforge.net/projects/portableapps/files/Mozilla%20Firefox%2C%20Portable%20Ed./Mozilla%20Firefox%2C%20Portable%20Edition%2047.0.1/
and I'm using it with Firebug only for development. According to Firebug's website 47 is the last compatible version of Firefox:
https://getfirebug.com/downloads
To avoid compromising on security, for normal browsing I use updated version of Chrome.
Downgrading the version is not advisable, So instead of that go to the browser console and type your respective xpath in the mentioned syntax $x('path') to validate your XPath.
Or can find other similar plugin. So far I find the Plugin 'Xpather' in http://xpath.alephzarro.com/ link.
But I still would like to reactivate Firebug to rework by setting the preferences browser.tabs.remote.autostart,
browser.tabs.remote.autostart.1 and
browser.tabs.remote.autostart.2
to false via about:config.
I've opened a Firefox today, hit the Firebug button and it showed me that in the new version it is integrated into the developer tools.
I hit ok and realized that it doesn't work at all (everytime using Inspect Element the <body> element is selected). So I would like to revert that setup back, but I cannot find where to switch it. I tried to reinstall Firebug, but that setup is stored somewhere so it automatically starts the DevTools instead of Firebug.
Any help how to revert back to the classic Firebug?
As I wrote in the Firebug discussion group, that the <body> element is selected first before the actual element you inspected is a bug and I've already filed a bug report for it.
There is also a bug related to the Inspect Element with Firebug option, which opens the DevTools, but doesn't actually select the inspected element. This bug got fixed in Firebug 2.0.19 by removing the option (so there's just the Inspect Element option left, which works as explained above).
As mentioned in my answer to a related thread, you may be able to reenable Firebug by setting the preferences browser.tabs.remote.autostart, browser.tabs.remote.autostart.1 and browser.tabs.remote.autostart.2 to false via about:config.
These settings control whether Firefox works in multi-process mode (separate processes for its UI and the websites). Unfortunately Firebug is incompatible with that mode.
Note: This is a temporary solution, because the multi-process mode will be mandatory at some point and the preference will be removed. Also, starting from Firefox 57 only WebExtensions will be supported and Firebug is based on different APIs, so it definitely won't work anymore at that point.
Another way is to install an old version of Firefox like 48, disable automatic updates and install Firebug there. Though, having said that, this option is not recommendable (at least not long term), because you will miss important (security) bug fixes and new features.
In additional to #Sebastian Zartner's answer, (from Firebug's website):
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.
More about your question:
Firebug is not working with Firefox version 50.0
Why got Firebug removed after updating Firefox to version 50?
I'm developing a web app and want to make sure that it runs as intended on all major browsers. I've downloaded Chrome, Firefox, Opera, Safari and IE to test the app, but I want to make sure it works fine on previous versions of these browsers too.
I know I can download previous versions of Opera from here, and in IE I can select 'Browser Mode' from Developer Tools section.
Is there any way I can test my app on previous version of Chrome, FF and Safari?
I've never really had a problem with something not working in an older version of these browsers. The only compatibility checks I do are with older versions of IE. The reason is that a new version of IE changes a lot but the others come out with new versions so frequently and have automatic updating (you don't even notice it in Chrome) that not only is there (probably) not a significant change to the rendering engine from one version to the next, (pretty much) everyone using it is on the latest version anyway.
That being said, there are some websites that show you screenshots of how a page looks in various browsers.
Browser Shots comes to mind.
http://www.brokenkeyboards.com/btfm/
http://meineipadresse.de/netrenderer/
http://browsershots.org/
I'm working on a corporate intranet and we have recently redesigned it using all sorts of CSS3 goodness as specified by a design agency. Our corporate standard browser is (still) IE8 so in order to make the CSS3 work I employed CSS3 PIE (http://css3pie.com/) which recreates the CSS functionality using VML via a .htc file - and it works great. However I've noticed that the http_referer value for pages viewed in IE8 is being returned as the location for pie.htc instead of the actual referring page and it was working just fine before the redesign. Firefox is tolerated as an alternative browser and for pages viewed in that browser all the http_referer values are as they should be. This is causing quite a headache for forms which redirect using this variable, as well as the logs which dump various environment variables to database for easy querying - and the guys who analyse the stats aren't remotely happy!
I have flagged this with the developer of CSS3 PIE and it's a mystery to him, but before I register a bug I wanted to see if it might be some failing of IIS or some setting I've missed in it (I'm using version 6 on Windows 2003). We have an Linux server with Apache as well for different purposes which I redesigned using the same technique and that doesn't seem to be displaying the same behaviour.
Does anyone have any related experience with PIE or any other .htc files on IIS which they were able to solve? Or is it some kind of IE8 bug that will never be fixed?
we experience the same issue. We removed it from the html. It could be an IE bug, I don't see any reason why the referer of the .htc should be the same as the page.