Friday, May 16th, 2014 05:23 pm
help for me plz
Question for the masses: does anyone know what in Firefox would cause Dreamwidth's expand function not to work in threads?
It works just fine when I'm at work, where I have Firefox installed. At home and at work, I'm using the same version of Firefox, Adblock and NoScript are installed and disabled, and yet, Expand works there and doesn't when I'm on my laptop. I've done everything short of bursting into tears--and trust me, it's a close thing--to work out the difference.
Anyone have any idea? Seriously, this is annoying.
Also, and not ashamed--I am totally playing Farmville 2: Country Escapes now that it's on Android and I don't have to access Facebook. I would hate myself, but there are acrobatic pigs and sheep who bellyflop in sync. Who the hell resists that? If anyone else is playing, I'm signed in through Google+, not Facebook, and seriously, acrobatic pigs. In sync.
ETA: Tentative solution that so far is working: disabled Greasemonkey, disabled "LJ Thread Expander" enabled Greasemonkey again, and problem solved. So far. Will update if that changes.
It works just fine when I'm at work, where I have Firefox installed. At home and at work, I'm using the same version of Firefox, Adblock and NoScript are installed and disabled, and yet, Expand works there and doesn't when I'm on my laptop. I've done everything short of bursting into tears--and trust me, it's a close thing--to work out the difference.
Anyone have any idea? Seriously, this is annoying.
Also, and not ashamed--I am totally playing Farmville 2: Country Escapes now that it's on Android and I don't have to access Facebook. I would hate myself, but there are acrobatic pigs and sheep who bellyflop in sync. Who the hell resists that? If anyone else is playing, I'm signed in through Google+, not Facebook, and seriously, acrobatic pigs. In sync.
ETA: Tentative solution that so far is working: disabled Greasemonkey, disabled "LJ Thread Expander" enabled Greasemonkey again, and problem solved. So far. Will update if that changes.
no subject
From:(- reply to this
- thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)
no subject
From:(- reply to this
- thread
- link
)
no subject
From:Best suggestion: do a winnowing test. Disable all extensions, check to see if it works (it should). Re-enable half of your extensions, see if it works: if it doesn't work, the culprit is in the half you just re-enabled, if it does work, the culprit's in the other half. Once you've IDed which half the culprit's in, divide that half into halves again, and enable half of them. Repeat ad infinitum until you've got it narrowed down to just one extension. (Or, if it's Greasemonkey that's the culprit, do a winnow on your scripts using the same principles.)
Sometimes the cause can be extension conflicts, which is harder to troubleshoot and results in you sitting there and testing each extension against all the others in combination and can take fucking forever, but usually you can nail it within 20 minutes or so. (Then, of course, you have to decide which is more important, the extension or the thread expand function.)
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:....my life, God.
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:wheeeeeeeeeeeeeeee
at least you found it!
(- reply to this
- parent
- top thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)
no subject
From:(- reply to this
- thread
- link
)
no subject
From:(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)