I am running Firefox on Ubuntu 15.04 64bit and using the KDE 5 framework and KWin. Previously, using KDE 4 I was heavily using virtual desktops for completely different t…
I am running Firefox on Ubuntu 15.04 64bit and using the KDE 5 framework and KWin.
Previously, using KDE 4 I was heavily using virtual desktops for completely different tasks. As things changed with KDE 5, I am forced to use what they call Activities.
I also almost solved the problem of Firefox not playing nice with KDE in general and in specific to the Activities by using a different profile for each Activity.
The actual problem:
Each time I click a link inside some application inside a KDE Activity, the following message window pops up: "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system."
Of course, when there is no Firefox instance running yet with the desired profile, any link opens up as expected with a new instance, just not a second or third or ... (which makes me copy'n'paste, which in turn makes me loose precious time and is just annoying).
So, I don't know how the internal communication of Firefox works but I only start Firefox with the options "--new-instance" to avoid getting a new window of the very first instance and "-P" for the profile.
UPDATE Although the "solution" found was to make use of the -remote "openURL(<url>)" command line argument, that argument is being deprecated and will be removed very soon (if it isn't removed already), see details here: https://bugzilla.mozilla.org/show_bug.cgi?id=1080319
Has there been a change on the HTML Datalist/text input elements behavior between Firefox 35 and Firefox 36?
I have a text-box input bound to a datalist via list attribute, one would type on the text-box to search for items. Upon hitting "Enter" key or "Search" button an XMLHttp…
I have a text-box input bound to a datalist via list attribute, one would type on the text-box to search for items. Upon hitting "Enter" key or "Search" button an XMLHttpRequest Object would be invoked as seen on the last image (starting from left to right).
If the searched items are available, in Firefox v35 the text-box would automatically be populated displaying a drop-down of the items, whereas in Firefox v36 & v37 the text-box does not automatically get populated. One has to click outside the text-box, to remove focus, and double-click again on the text-box to be able to see the drop-down of the items.
Attached please see screen-shots to help visualize my scenario. First image(Left-Right) shows behavior in v35, whereas this haviour is not available in v36 & v37 (image in the middle) in this case if I want to see the drop-down I would have to click outside the text-box and double click again inside it then it would show.
I would like to know if the difference in behaviour was purposely changed from these versions of Firefox.