Can only copy text with default profile
We have a system that generates HTML output, but the URL does not identify the output as such.
This is the URL: https://{ServerName}/analytics/saw.dll?Go
... where {ServerName} contains a valid server name.
I can select the output and copy/paste it, but some of my colleagues cannot. They can't even select the text.
When they save the page as test.html and then open the file, in FireFox, then they *CAN* select text. However, if they save the file as test.htm, they *CANNOT* select text.
It looks like for them FireFox is unable to determine if the HTML output is in fact HTML.
But like I said: I can always select the output. Also if I save the output as test.html and also when it is called test.htm.
We are unable to figure out which setting causes this behavior that it works for me but not for them.
When I create a new profile with the profile manager of FireFox, I can also not select text anymore.
I've tried to empty the new profile and copy everything from the working profile, but still I cannot select text with the new profile.
When I do the following:
- copy the default profile (the one that works for me) to "default.copy" - rename the default profile to "{code}.default.original" - rename "default.copy" to "{code}.default"
... then the copied and renamed profile works fine.
When I do the following:
- create a new profile "{code}.test" - copy the default profile (the one that works for me) to "default.copy" - rename the default profile to "{code}.default.original" - rename "default.copy" to "{code}.test"
... then the new profile does NOT work.
I saved the HTML for both the "{code}.test" and "{code}.default" profiles by right-clicking and choosing SAVE AS... I looked at the css files that were stored in the folder that comes with the file. It appears for the "{code}.test" profile, the views.css contains a lot of these:
user-select:none;-moz-user-select:-moz-none;-khtml-user-select:none;-webkit-user-select:none;
... whereas the "{code}.default" profile does not have this.
Where does this come from?
This drives me insane. What do I need to set for a new profile to make sure I can select text in output that is not identified by their extension?
Изменено AHiemstra
Все ответы (4)
The DOM Inspector should be able to tell what style rules are applied and in what CSS file they are found if you can't use the Inspector.
- DOM Inspector: https://addons.mozilla.org/firefox/addon/dom-inspector-6622/
The question I have summarized:
I have a default profile. With it, I can select text in the output of a web site.
Now I create a new profile. With that profile, I CANNOT select text in the output of the same web site.
-o-o-o-
When I do a SAVE PAGE AS for both profiles, I noticed that the saved views.css for the new profile contains additional:
user-select:none;-moz-user-select:-moz-none;-khtml-user-select:none;-webkit-user-select:none;
... statements.
QUESTION: Why does Firefox insert these statements into the views.css stylesheet - thus actively preventing the selecting of text?
I can override this with a userContent.css stylesheet that looks like this, but WHY is this necessary for the new profile?
@-moz-document domain(myserver.com){
.PTCHC0,.PTCHC1,.PTCHC2,.PTCHC3,.PTCHC4,.PTCHC5,.PTCHC6,.PTCHC7,.PTCHC8,.PTCHC9,.PTCHC10 {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTCHCT0,.PTCHCT1,.PTCHCT2,.PTCHCT3,.PTCHCT4,.PTCHCT5,.PTCHCT6,.PTCHCT7,.PTCHCT8,.PTCHCT9,.PTCHCT10 {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTRHC0,.PTRHC1,.PTRHC2,.PTRHC3,.PTRHC4,.PTRHC5,.PTRHC6,.PTRHC7,.PTRHC8,.PTRHC9,.PTRHC10 {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTRHCT0,.PTRHCT1,.PTRHCT2,.PTRHCT3,.PTRHCT4,.PTRHCT5,.PTRHCT6,.PTRHCT7,.PTRHCT8,.PTRHCT9,.PTRHCT10 {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTLHC {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTHT {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTHT {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTVC {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTDC {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTDCT {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTDT {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.PTDTT {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.TTHC {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.TTHCHC {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; }
.TTHT {user-select:all !important; -moz-user-select:-moz-all !important; -khtml-user-select:all !important; -webkit-user-select:all !important; };}
There are dom.event.* prefs that might have affect in case you have changed them in your current profile.
- dom.event.clipboardevents.enabled
Thank you for your hint.
Unfortunately both the Default profile as well as the new profile have:
dom.event.clipboardevents.enabled;true