*It's.
Are you using it? This is how it interacts when used from the free nodelet–
The XSS Auditor refused to execute a script in 'http://perlmonks.org/?' because its source code was found within the request. The auditor was enabled as the server sent neither an 'X-XSS-Protection' nor 'Content-Security-Policy' header.
| [reply] |
| [reply] |
From what I understand this approach is wasting resources.
I don't see the point to return several kb of html with the full node just to let JS parse the votes out. (Except maybe for a prove of concept of DOM manipulation)
update
as I already said
> > > > Adding a new vote-interface shouldn't be harder
| [reply] |
From what I understand this approach is wasting resources. :) Not that many extra ones that aren't wasted already
Its very much like hitting talk or refresh in chatterbox
It is a common viewing pattern to view a node, vote on it, then scroll down, to see a reply you like, vote on it, and so on
Also common to open a node in a new tab and do the same
So resource wasting? Not really
But it doesn't have to do that, code could pick a different node that returns less byes, like 162 bytes
Or it could simply "cue" votes and cast them every 30 seconds at a cost of under 500 bytes
as I already said as I already agreed :p
| [reply] |
> Its ...
*It's
> ... very much like hitting talk or refresh in chatterbox
The difference here is that CB has not only already plenty of lean alternatives (like sidebar) but also "tickers" which could be called with JS support in the CB nodelet (hence AJAX )
OTOH no voting ticker yet.
| [reply] |
