Hevilmystic
said
:
Quick suggestion, if you open up this:
http://i.imgur.com/rt6vSp7.png
It stops you from clicking elsewhere on the page. Is it possible for you to make it so if you click outside of that box, it closes it?
~ Pink for Papa
Probably could use Escape to remove the alert somewhere around line 364. Like so:
$(document).keydown(function(e) {
if (e.which == 27) {
setTimeout(function() {
$('#a_holder').remove();
}, 50);
}
});
Hevilmystic
said
:
It stops you from clicking elsewhere on the page. Is it possible for you to make it so if you click outside of that box, it closes it?
The preventing of clicking the page was intentional, I can't remember why though. There are already 3 methods for closing it. [ctrl + c] closes it, selecting copy closes it, the close button closes it too. Tbh I'm not sure if it needs another close method, after all it auto closes once it's been used.
I guess what I'm asking is what makes it hard to use, because to me closing it should be from using the interface or the interface shortcut keys, not clicking elsewhere on the page. I'm also wondering is not working properly and not closing after copying the QFC?
The escape key to close would make more sense from a design point of view, but four different close methods for something that has one function seems excessive to me.
I'm fine with making improvements, I just need convincing on this one, assuming it's working properly and if you open it and don't wish to use it, the close button is fine imo.
Edit: just re-read this post and I'm not sure if I came across as rude. Rather than edit I'll add a bit
If allowing the page to be interact-able will improve usability that's something I'll look into. I don't want things to be awkward or hard to use, but at the same I don't want to add things just for the sake of it. I don't always need a practical reason to do something, aesthetics or even because it's fun are reason enough.
I just want to make sure I'm addressing the right area, of the things that could be improved with the Quick QFC, that's the last thing I'd have though it needed.
05-Oct-2014 13:35:36
- Last edited on
05-Oct-2014 16:24:53
by
Indecent Act
Double posting, a frequent occurrence by many forum users, is something I think could be easily tackled with Linkify. While I do not know if it has been suggested in the past, I think it's a topic that could be addressed and resolved in some cases. The answers in jQuery might not play nicely with the main script, but it's an item that came to mind.
Now I think it might be redundant as the
noSpamSubmit
function exists within Global: http://www.runescape.com/js/global-69.js it just does not seem to work as intended. Well that's all for the time being. El Psy Congroo.
This actually been discussed a little in the past. I haven't done anything to try to prevent double posts. I'm not entirely sure if the issue is client or server side. The other thing is, I have only had it occur once in my years of foruming. If I do something it will be very hard to actually know if it works or not.
However I'm not against the idea of trying.
As you may have noticed the problem with that method you linked, is that on these pages the submit form has two methods, a preview and submit. That script would prevent submitting if previewed first.
Edit: I'm tired, that won't apply since it's a new page that's loaded from the form submit/preview.
Anyway it's definitely something I look into
05-Oct-2014 13:48:00
- Last edited on
05-Oct-2014 16:30:56
by
Indecent Act
That's fine. I understand that there can be too many ways of exiting an item and that it's very difficult to test how double posting occurs. It's not a pressing matter and I value that not everything can be fixed in Javascript or client side.