I posted my question on meta, how would I know this has been solved if it is bug, any stack exchange developer will write this in answer, meta.stackoverflow.com/questions/226322/…
@tgmcians Things take a long time here, which is probably why 6 to 8 weeks is mentioned so much :). It doesn't seem that your issue is especially critical (security-wise), so if it is a bug, it likely won't be taken care of for a little while.
// We need to parse the url on the client, because the History plugin generates different "permalinks" for IE
// compared to modern browsers. More specifically, the reviewTaskId is in the location *hash* on IE.
// Also, the History plugin rewrites wonky IE-generated permalinks on page load on modern browsers, but this
// happens before this function is called.
//
// For example, IE might generate this permalink:
// http://meta.stackoverflow.com/review/low-quality-posts/3180#./2394?&_suid=134166978302009324214523754495
@jan Sorry about that. I thought that he was adding to the answer- which is why I think the reviewers don't deserve the ban hammer. Perhaps they thought what I did, so maybe just a slap on the wrist would be better? What do you think?
If you are a 1 rep user, and click on the uvpote icon, what message is displayed? I tried from being an anonymous user and it asks for login credentials, but I was curious from an already logged in, 1 rep user. Anyone know? I couldn't find it on meta.
Not intentionally. I was really just trying to figure out the text for the upvote error message.
Came across this in the source code though, thought it was amusing: "FireBug seems to be enabled, which can sometimes interfere with voting;<br>please refresh the page to see if your vote was processed.<br><br>If this persists, consider disabling FireBug for this site."
Oh well, maybe someone can ping me later if they know the message that shows.
> Doorknob reviewed this 20 secs ago: Reject This edit is too minor; suggested edits should be substantive improvements addressing multiple issues in the post. The Guy with The Hat reviewed this 1 min ago: Reject This edit is too minor; suggested edits should be substantive improvements addressing multiple issues in the post. Robert Scholte reviewed this 1 min ago: Approve dpassage reviewed this 2 mins ago: Approve lokoko reviewed this 2 mins ago: Reject This edit is too minor; suggested edits should be substantive improvements addressing multiple issues in the post
Easy snippet to copy/paste to console to fight backtick fires:
var f = function() {
var s = $(this).val();
var cursorPosition = this.selectionStart;
var lastBacktick = s.indexOf("`", cursorPosition);
var firstBacktick = s.lastIndexOf("`", lastBacktick - 1);
s = s.slice(0, lastBacktick) + s.slice(lastBacktick + 1);
s = s.slice(0, firstBacktick) + s.slice(firstBacktick + 1);
$(this).val(s)
};
$('textarea').on('click', f)
3
Now when you click in the edit box it will debacktickify whatever you clicked! To turn it off:
