Originally Posted by concealer404
(Post 1517883)
Happens to me about once out of every ten cats given. Windows 10, Firefox.
|
when you click the cats, it makes an ajax call to send the data and return the new props.
there's also an href="" url for the link to follow. if you follow that code youll get the confirmation page, as it's doing the props using a query string in the url to submit the props and not the asynchronous ajax call: https://www.miataturbo.net/misc.php?...65a0e889390e3d i think some browsers are failing to follow the rel=nofollow html5 code and navigating through the link. probably should just remove the href, unless you can use it as a backup if the ajax does not return a success. i helped write the props code long ago. |
I just poscat you and it incremented by one without opening a new window.
so like dear mechanic my car makes this noise: GRRNT GRRNT GROOOOOCH but only when I'm alone and not recording it |
Originally Posted by y8s
(Post 1517931)
I just poscat you and it incremented by one without opening a new window.
so like dear mechanic my car makes this noise: GRRNT GRRNT GROOOOOCH but only when I'm alone and not recording it |
Like I said, each cat is technically a hyperlink. But there's an attribute to prevent browsers from actually following the link (the original implementation of the props code), and instead it follows some php code, i believe parsing the data out of the query string of the url, and that will update the props without navigating to a new page using ajax.
It seems that for some reason, certain browsers are failing to following the rules of rel="nofollow". |
funny, i just gave you props and it opened in a new window. I've never seen that before, and didn't do anything but reload this page since it was still open in the tab from yesterday.
|
Originally Posted by Braineack
(Post 1517921)
when you click the cats, it makes an ajax call to send the data and return the new props.
there's also an href="" url for the link to follow. if you follow that code youll get the confirmation page, as it's doing the props using a query string in the url to submit the props and not the asynchronous ajax call: https://www.miataturbo.net/misc.php?...65a0e889390e3d i think some browsers are failing to follow the rel=nofollow html5 code and navigating through the link. probably should just remove the href, unless you can use it as a backup if the ajax does not return a success. i helped write the props code long ago. |
i basically just changed the + and - to the cats. I believe the code was mostly written by a Canadian.
|
Scott loves to mess with me.
But that's ok. I enjoy it. |
We're updating some software today, so blame Nolan if anything breaks.
|
Nolan who? Robb is the one who breaks things now.
|
Originally Posted by Robb M.
(Post 1519688)
We're updating some software today, so blame Nolan if anything breaks.
It stands to reason that these are related. |
I blame Dolan
https://cimg2.ibsrv.net/gimg/www.mia...81549e737b.jpg |
Ok, serious time:
This is what the message composer looks like now (with hovertext shown for several of the buttons): https://cimg7.ibsrv.net/gimg/www.mia...0992e4a058.png On the plus side, Indent appears to be fixed. So thanks for that. [Also, [noparse] is working again. [B]Nice. [/B] https://www.youtube.com/watch?v=aUWLT02Daoo (Interesting, it's still being presented as a clickable URL, although I did not use a [URL="https://www.miataturbo.net/tag."] tag. Let's try this: White house spokescats still deny that [/URL] [ame="https://www.youtube.com/watch?v=aUWLT02Daoo"]the administrator[/ame] of an El Segundo-based automotive forum has had any contact with, or influence over (...) Wow, that's even more broken than it was before. Looks really freaky in the composition window when I switch out of [source] mode. And I don't know where the hell it's getting [/ame] from... Ah, well. Progress. |
|
Originally Posted by Joe Perez
(Post 1519836)
Ok, serious time:
|
It should -=> NOT <=- do any parsing when the url is inside a [noparse][/noparse] section.
For instance, let's say I'm writing something, and I want to say something to the effect of "... and you can see more proof of this in Any Of These Three Videos," where each of the five highlighted words is surrounded by a [noparse][/noparse] tag, such that the word is clickable and leads to a youtube video. In other words, I specifically want the forum to NOT automatically embed the video (which noparse is correctly preventing), but then I also don't want it trying to interpret the url (which it is trying to do, and failing.) Example: I have already laid down a noparse, and now I am going to say that you should look at [ame=https://www.youtube.com/watch?v=5czSr2UD7-Q]This Amazing Cat Video[/ame] before it's too late! Here's what the sentence above looked like while I was typing it: https://cimg3.ibsrv.net/gimg/www.mia...a56d315c40.png Same problem with Twitter links, which have been quite profuse of late in the political press. |
i have never in my life seen noparse used on a vB. here we use code to achieve that.
- |
i will report the noparse issue.
|
Hey @Robb M. , i don't know if you knew this about us, but we really really really really don't like fuzzy pictures.
Like, for real. AND, it is unlikely that at any time in the foreseeable future, we will begin liking fuzzy pictures. Like, for real. If at any point, you or your overlords consider that maybe we are growing out of our huge dislike of fuzzy pictures, it is safe to assume that we aren't/haven't. Like, for real. Love, Everyone On This Entire Forum. |
All times are GMT -4. The time now is 09:27 PM. |
© 2024 MH Sub I, LLC dba Internet Brands