Dan Cameron: Comment Quicktags + 1.101 at Scattered
Anonymous
· 4 years ago
i am coming from babygotblog.com, just thinking to install this plugin.
look very cool right ?
vamsi
· 4 years ago
i am coming from babygotblog.com, just thinking to install this plugin.
look very cool right ?
Syd Lexia
· 4 years ago
How do I mod the quicktags to fit my site style? I just get the ugly basic grey Windows buttons...
Syd Lexia
· 4 years ago
Hi, I just wanted to say that I just found your quicktags plugin for comments and I absolutely love it. However, I was wondering if there was a way to mod it to keep the tags always displayed or at least to have them start open. Also, is there a way to prevent the menu from dropping down to another line when it is open?
I found the answer to my first question was actually embedded in the author notes for the PHP file. My bad.
Dan
· 4 years ago
I don't know why it drops down so I haven't an idea in fixing it. But you can have it open all the time by modding the plugin file, I forget the code to delete but if you look at it you should find it no problem.
BUSTED!!! - PS, how come you have to be logged in to comment on this? Is it because it's an old post?
Dan
· 4 years ago
Didn't even notice that comment until today. Wierd, good thing I Jared pointed it out because not only did I include that license but I forgot to include the .js file in the download.
DOH!!
Owen
· 4 years ago
No worries. :)
I think you might have done something odd with the plugin, though. It seems like you rolled back more than you needed to. Did you mean to remove the extra css recommendations that you added for your version?
Chris C
· 4 years ago
Hi there. I arrived here via a Google search while trying to isolate an issue with the page-refresh behavior on certain blogs when browsing with Firefox or Opera.
To be specific: The refresh (reload) issue on the pages in question is that the browser doesn't return to the spot on the page where it had been prior to refresh, and instead defaults to the top of the page. That can be quite frustrating when one is trying to keep up with, say, a bustling comments thread.
After some poking around, I've begun to suspect that the culprit is something in Alex King's quicktags script, because that script is the one trait that all these problematic sites have in common. Hence the Google search that got me here.
Sorry to hog your comments thread with this post from somebody you've never met. But after seeing that you just happened to update this post today, it seemed like a good shot to see if you've got any insight on the issue I've described.
Thanks so much... Chris Cordella
Dan
· 4 years ago
Thanks again Owen I accidently uploaded the wrong archive.
Chris I haven't really seen that particular problem here but if you do I would like to know. Don;t worry about commenting, the internet is "free"; supposidly anyways.
Chris C
· 4 years ago
Hi, Dan. Thanks for the quick response.
If you're using IE, you won't encounter the browser behavior I've described. Note sure why it's immune, though maybe it's because IE is ignoring some W3C standard.
But to answer your specific question: Yes, I am seeing that problem here on your site. Let's say, for instance, that I've scrolled down here toward the bottom of the page and am reading our latest comments. Then I click the reload button in Firefox to refresh the page to see if anybody's added a new comment. Instead of returning me down here to this part of the page, the browser starts back at the top, and I have to manually scroll to get back down here.
It's as if there's some kind of anchor tag somewhere telling the browser to always go to X position on the page. Like I say, IE apparently pays it no attention; Firefox and Opera, on the other hand, do what it says.
Which browser are you using?
Dan
· 4 years ago
Yeah that is wierd, guess I've never noticed it since I use an aggregator.
So you think it's AK's QT plugin?
Even if it is, I think it's worth the sacrifice.
JaredB
· 4 years ago
Each comment has an anchor (A tag) that you reference to jump down to that particular part of the page when it loads (this is the # part on the end of the URL). This is the traditional way to load a page and scroll it to a given position. This should work fine in both Firefox and IE (and all other browsers for that matter).
Since it sounds like you might know this already, I'm assuming that you're either saying that you're trying one of these links (with an anchor) and the page is not scrolling, or you're trying a link without an anchor and expecting the page to scroll in some other way.
Hitting "Refresh" will basically just reload the URL that's in your address bar, so if it's got the # in it, it should work fine. If not, it will (and should) just load the page and not scroll you down, unless there is some other scripting at work, which would seem kind of pointless since there's a non-script way to scroll people to a certain point in the document.
Perhaps it's that the links do reference the anchors, but the anchors are not being drawn on the page, because of a change to the template of the blog, etc.? I don't think that's the case here, but it could explain other instances.
All Comments
look very cool right ?
look very cool right ?
I found the answer to my first question was actually embedded in the author notes for the PHP file. My bad.
Thanks!
DOH!!
I think you might have done something odd with the plugin, though. It seems like you rolled back more than you needed to. Did you mean to remove the extra css recommendations that you added for your version?
To be specific: The refresh (reload) issue on the pages in question is that the browser doesn't return to the spot on the page where it had been prior to refresh, and instead defaults to the top of the page. That can be quite frustrating when one is trying to keep up with, say, a bustling comments thread.
After some poking around, I've begun to suspect that the culprit is something in Alex King's quicktags script, because that script is the one trait that all these problematic sites have in common. Hence the Google search that got me here.
Sorry to hog your comments thread with this post from somebody you've never met. But after seeing that you just happened to update this post today, it seemed like a good shot to see if you've got any insight on the issue I've described.
Thanks so much...
Chris Cordella
Chris I haven't really seen that particular problem here but if you do I would like to know. Don;t worry about commenting, the internet is "free"; supposidly anyways.
If you're using IE, you won't encounter the browser behavior I've described. Note sure why it's immune, though maybe it's because IE is ignoring some W3C standard.
But to answer your specific question: Yes, I am seeing that problem here on your site. Let's say, for instance, that I've scrolled down here toward the bottom of the page and am reading our latest comments. Then I click the reload button in Firefox to refresh the page to see if anybody's added a new comment. Instead of returning me down here to this part of the page, the browser starts back at the top, and I have to manually scroll to get back down here.
It's as if there's some kind of anchor tag somewhere telling the browser to always go to X position on the page. Like I say, IE apparently pays it no attention; Firefox and Opera, on the other hand, do what it says.
Which browser are you using?
So you think it's AK's QT plugin?
Even if it is, I think it's worth the sacrifice.
Since it sounds like you might know this already, I'm assuming that you're either saying that you're trying one of these links (with an anchor) and the page is not scrolling, or you're trying a link without an anchor and expecting the page to scroll in some other way.
Hitting "Refresh" will basically just reload the URL that's in your address bar, so if it's got the # in it, it should work fine. If not, it will (and should) just load the page and not scroll you down, unless there is some other scripting at work, which would seem kind of pointless since there's a non-script way to scroll people to a certain point in the document.
Perhaps it's that the links do reference the anchors, but the anchors are not being drawn on the page, because of a change to the template of the blog, etc.? I don't think that's the case here, but it could explain other instances.