[JandS]

Another wishlist item. Could there be a "Thank you for posting" (however worded) independent of the Like button?

It seems as if like Like is doing multiple duty as a reaction and very often one does not want to "Like" something (e.g. an awful news event) but would like to thank the poster for posting about it.

 

[Mike Lang]

Anybody else having a problem with FireFox/Win10?

I had to dust off FF (don't trust it anymore) but it looks fine with Win10.

 

[eddyj]

Another wishlist item. Could there be a "Thank you for posting" (however worded) independent of the Like button?

It seems as if like Like is doing multiple duty as a reaction and very often one does not want to "Like" something (e.g. an awful news event) but would like to thank the poster for posting about it.

Why not use one of the other reactions?

 

[JandS]

I had to dust off FF (don't trust it anymore) but it looks fine with Win10.

Thx @Mike Lang , I'll disable any other extensions and see what happens.

 

[SteveD]

Another wishlist item. Could there be a "Thank you for posting" (however worded) independent of the Like button?

It seems as if like Like is doing multiple duty as a reaction and very often one does not want to "Like" something (e.g. an awful news event) but would like to thank the poster for posting about it.

You can always use the SAD 🙁 instead.

 

[JandS]

Why not use one of the other reactions

Help!! does nobody get the distinction??

 

[eddyj]

I get the distinction, but at least we have a bunch of options now, not just Like. Thanks is just another reaction, but it did not make the list.

 

[JandS]

I had to dust off FF (don't trust it anymore) but it looks fine with Win10.

What version of FF did you try? I'm 96.0.1 (64-bit) it updated yesterday the 14th.

 

[Mike Lang]

What version of FF did you try? I'm 96.0.1 (64-bit) it updated yesterday the 14th.

Worked fine on both 95 & 96.

 

[Rob Helmerichs]

Another wishlist item. Could there be a "Thank you for posting" (however worded) independent of the Like button?

It seems as if like Like is doing multiple duty as a reaction and very often one does not want to "Like" something (e.g. an awful news event) but would like to thank the poster for posting about it.

There are now a number of different "Likes" you can give a post...such as the one I just gave yours.

[edit] Oops, didn't see the following page!

 

[eddyj]

There are now a number of different "Likes" you can give a post...such as the one I just gave yours.

[edit] Oops, didn't see the following page!

Smeek, is that you using Rob's account?

 

[astrohip]

Why not use one of the other reactions?
View attachment 67776

Didn't realize this until now. You earned for this!

 

[JandS]

Anybody else having a problem with FireFox/Win10? It just started this morning about 8:30am PST, the page layouts are all wacked up. I don't use any of the scripting mods and have disabled NoScript completely but no joy yet.

It starts with huge page-filling Tivo community logo then it just flashes away and the push notification wording with scrambled design comes up but I can't click on any of the "no" "never buttons" so after that nothing works.

Chrome is ok.

@Mike Lang, I'm pasting two screenshots from FF 96.0.1 (64-bit) of the HH forum as compared to the SubaruOutback.org forum. TCF doesn't work, SubaruOutback works perfectly, the same as it always has for me.

1. The TCF is a link to the grocery thread.
2. Note that I zoomed down to 30% to show that the still page-size TCF logo is superimposed on the actual thread itself, as shown by the aqua arrow.
3. The javascript choices Enable Push Notification Not Now Never don't work to dismiss the dialog box. They highlight or underline, but don't do anything.

I suppose it's possible that if there were the same push notification dialog on the Subie forum it, too, would cause the same lockup in FF. However, the push notification did NOT cause this lockup yesterday, I was able to dismiss the dialog just fine and it did not expand to fit page size. Could it be that the push notification was changed somehow between last night and prior to 8.30am PST Saturday?

 

[dswallow]

@Mike Lang, I'm pasting two screenshots from FF 96.0.1 (64-bit) of the HH forum as compared to the SubaruOutback.org forum. TCF doesn't work, SubaruOutback works perfectly, the same as it always has for me.

1. The TCF is a link to the grocery thread.
2. Note that I zoomed down to 30% to show that the still page-size TCF logo is superimposed on the actual thread itself, as shown by the aqua arrow.
3. The javascript choices Enable Push Notification Not Now Never don't work to dismiss the dialog box. They highlight or underline, but don't do anything.

I suppose it's possible that if there were the same push notification dialog on the Subie forum it, too, would cause the same lockup in FF. However, the push notification did NOT cause this lockup yesterday, I was able to dismiss the dialog just fine and it did not expand to fit page size. Could it be that the push notification was changed somehow between last night and prior to 8.30am PST Saturday?





View attachment 67798 View attachment 67799

I just updated Firefox to 96.0.1 (64-bit) and opened that link, then switched to 30% zoom, and all looks fine for me. Could something else you have installed be affecting it?

 

[Mike Lang]

@JandS - Since this is an isolated issue with your own device/browser, please use another thread to trouble shoot. We want to keep this thread focused.

Thanks

 

[morac]

Is there a way to make the contrast between read and unread threads in dark mode easier to see. The “bold” white is pretty close to the normal white. I think the main problem though is that the poster, date and forum name in a read post is also bolded. I can tell the difference between read and unread threads, but it takes more effort than just glancing at the list. For example:

 

[dswallow]

Is there a way to make the contrast between read and unread threads in dark mode easier to see. The “bold” white is pretty close to the normal white. I think the main problem though is that the poster, date and forum name in a read post is also bolded. I can tell the difference between read and unread threads, but it takes more effort than just glancing at the list. For example:


View attachment 67808

Assuming you're using Hank's Tampermonkey script? If so, wrong thread. But changing the line that does the read-thread adjustment to this may help you.

    $('.structItem--is-read').parent().parent().parent().css("font-weight","normal").css("opacity","0.5");

 

[morac]

Assuming you're using Hank's Tampermonkey script? If so, wrong thread. But changing the line that does the read-thread adjustment to this may help you.

$('.structItem--is-read').parent().parent().parent().css("font-weight","normal").css("opacity","0.5");

I’m not using any scripts as I’m using a tablet. This is what shows up by default in “dark mode”.

 

[PaulS]

Agreed with the above. The difference between read and unread threads in dark mode is minimal, which makes it difficult to differentiate between them. I am also not using any scripts to modify the site.

 

[eddyj]

Part of the reason for the script is that they are so hard to tell apart, and cannot be changed.