Yes, yes... That's what I meant. I should have written that in a better way .DavidIQ wrote:No, those settings are in the ACP. The forum admin is who decides what he wants to allow for signatures and what he doesn't. The user obviously shouldn't be in control of that.brunoais wrote: That's set using the ACP, right?
How about if only a small significant subset of the users don't like that kind of signatures but other like 'em? Doesn't it sound a better use case for this kind of thing?
What's the specific problem you have in mind?DavidIQ wrote:Not sure how I feel about that. There are so many people that have issues with cookie and a certain EU cookie law that comes to mind...brunoais wrote:No... I meant a js only approach. This is not required to use the forums. It's just a fancy thing, so js alone is perfectly ok, IMO.
Just use the storage interface or cookies to store... Simple as that.
If you keep using jQuery for those stuff, yeah. That will happen too much.Ger wrote: However: I can imagine a big slowdown when a frequent user keeps adding more and more user_id's to that list. With only a handful it wouldn't matter, but with hundreds or maybe even thousands user_id's to search through with JS I think some browsers will have a hard time. That could potentially result in bad user experience.
I think you forgot that there's something called stylesheets... Ya know... Those things where you write CSS rules you want the browser to follow... (just messin' with ya).
Anyway, using a simple querySelectorAll() we can deal with that easily.
(tested only on ff)
- Used 1223 comma separated elements in the selector (in 6152 characters for the whole selector).
- All selectors were made for a class attribute.
- I tested in the last page of this topic by copying what's in the @id attribute into the @class attribute.
- The selectors that would match were randomly inserted in the comma separated list.
- Got 5 Nodes as the result, which is the result expected.
- Time required: 50ms
Then I tested using jQuery.
I got bored after 30s waiting and so I killed the browser instance (yeah... the browser locked up). I think it wasn't using the querySelectorAll() and was searching in the DOM itself.
Don't forget that querySelectorAll() is supported by all of the most used browsers, firefox, opera, chrome, IE9, IE8(css2 selectors).
So... still got problems with slowness in finding the tags to hide, Ger?