|Account type:||Plus Account|
style: (S2) core: public, i18n: none, i18nc: none, layout: public, theme: public, user: custom,
cluster: HotWings (#13); data version : 8
scheme: dystopia; language: en_LJ
|Request sent from Beta:|
|Photo hosting migration:||done|
|Support category:||Entries [previous|next]|
|Time posted:||Wed, 21 Dec 2011 06:44:27 GMT (1 year ago)|
|Status:||closed (10 points to rebelsheart)|
I can no longer post comments in the new style. It remains a grayed out box even after I have typed. I tried walking away for five minutes in case it was a lag issue. It wasn't.
I'm using Firefox 8.0.1 on Mac OS 10.6.8.
It works on Chrome, but Chrome on my computer is a much slower browser and you really ought to be supporting Firefox in all of its configurations.
Diagnostics: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
Wed, 21 Dec 2011 07:03:23 GMT (1 year ago)
Thank you for your report and I'm sorry for the inconvenience. This was a temporary problem which we believe should be resolved at this time. If you are still experiencing trouble, please try clearing your browser's cache. If that does not help, please reply so we can investigate further.
Wed, 21 Dec 2011 07:34:14 GMT (1 year ago)
I just cleared my browser's cache and restarted my computer. It did not help.
Wed, 21 Dec 2011 12:20:33 GMT (1 year ago)
Just so you know, it still hasn't cleared up, in case you thought more time would do it.
Tue, 27 Dec 2011 19:44:39 GMT (1 year ago)
Other users have reported that they are able to use the new comment form by disabling the Greasemonkey add-on (or specific scripts within the add-on). If you are currently using Greasemonkey, can you please try this and let us know if the problem continues?
Mon, 02 Jan 2012 02:47:36 GMT (1 year ago)
Ah, yes. That does enable me to leave comments.
Which would be nice if I didn't have Greasemonkey enabled for a reason.
Oh well. I'll simply continue to view all journals in my style.
Mon, 02 Jan 2012 03:07:25 GMT (1 year ago)
It is likely that a specific script in Greasemonkey, rather than the extension as a whole, is causing the problem. If you re-enable the extension, you can disable individual scripts within it to see which one is causing the conflict.
Go to: previous open request
,next open request
Back to the list of open requests
Back to the support area