I think I found a bug in the forums. The text directly after a closing QUOTE will not allow a double hard-return.
This is quoted text
This is a line of text.
This is another line of text, separated by the first by two hard returns.
This should result in a blank line appearing between the two paragraphs.
While composing, every sentence in this post should be its own paragraph, with blank lines between them.
As you can see, there is no blank line after the text that follows a QUOTE, instead they are smooshed together, which makes it kind of hard to read.
Here is a pic which might help.
Looks fine to me. Are you using IE? The messageboards have been doing some weird things in Internet Explorer lately.
I'm using IE7 and it looks fine to me.
Senior Software Developer
|
At this point I'm not sure if this is a bug we've fixed or not. We've been making lots of changes to our HTML and style sheets over the past few days, and it's possible your browser is caching an older stylesheet. If that's the case then relaunching your browser or clearing your cache should do the trick. It's also possible that the HTML we're using now is incompatible with your browser, in which case, we have some fixing to do. What browser are you using?
|
I think I found a bug in the forums. The text directly after a closing QUOTE will not allow a double hard-return.
This is quoted textThis is a line of text.
This is another line of text, separated by the first by two hard returns.
This should result in a blank line appearing between the two paragraphs.
While composing, every sentence in this post should be its own paragraph, with blank lines between them.
As you can see, there is no blank line after the text that follows a QUOTE, instead they are smooshed together, which makes it kind of hard to read.
Here is a pic which might help.
Well, it looks like your browser is ignoring empty paragraphs, which is the case here with the double hard return after the quote. I've been noticing it also generating paragraphs within paragraphs in other instances so trying to sort this out and make it work like we want it to is a very high priority. There are a couple of things we are looking at in this area specifically and hopefully we will have a better solution soon.
That's a little oversimplified actually, but regardless, it's ignoring what should be an empty paragraph and thus, a line break.
it's possible your browser is caching an older stylesheet. If that's the case then relaunching your browser or clearing your cache should do the trick.
Everything is purged when the browser closes, so unless it's getting a fresh yet incorrect from a server with a bad cache, that's probably not it. (AFAIK my ISP doesn't use 'speedboost' caching or anything.)
It's also possible that the HTML we're using now is incompatible with your browser, in which case, we have some fixing to do. What browser are you using?
It happens with:
Firefox 3.6.23/MacOS10.5.8Firefox 3.6.22/WinXP
Firefox 3.6.24/WinXP
It looks normal in Safari 5.0.5/OSX and FF8.0/WXP but those are both terrible options.
Anyway, thanks for looking into it. I hope updating to a worse browser doesn't become required to use the forums. (I'm still fairly bitter about scripting being required. --which just bit me again, as without scripting I was still somehow signed in, and composing this reply, yet on hitting Submit was booted to the main page. Text edit backup post saves the day again)
(And as long as I'm here, I'll mention my desire for a monospaced font option! It would make ASCII grids and stuff much easier.)
Something changed. The paragraph thing seems fixed.
The sub-forum post lists (like if you click "Website Feedback" and browse the threads) are a little strangely spaced out now. I don't think it's a full blank line, but it seems like a lot of padding between the horizontal lines and the text of the thread title (Above and Below).
Anyway, thanks for the incredibly speedy work!
|
|
Something changed. The paragraph thing seems fixed.
The sub-forum post lists (like if you click "Website Feedback" and browse the threads) are a little strangely spaced out now. I don't think it's a full blank line, but it seems like a lot of padding between the horizontal lines and the text of the thread title (Above and Below).
Anyway, thanks for the incredibly speedy work!
Looking at it in 3.6.24 now. There does appear to be an extra pixel or two surrounding the hr that is pushing it up on that browser. Not sure why. I'll see if I can find a tool that will give me the metrics.
For the record, I hated the new firefox after 3.6.24 and immediately switched back to 3.6.24 but once I took away all of the chromifications, I found it a lot better for me to use and the development window is fantastic, so every time I download a new copy I take all of the new stuff out and make it work like old firefox with the new rendering engine. That should be a single button option I think. ^_^
Anyway, I'll take a look. We're now in almost strict mode which means a rendering quirk sometimes appears in the box-model for various elements if the browser wasn't setup to handle the newer box model perfectly. Also it means we have to be a little more careful about how we do certain things but it also means going forward, it will be easier to keep things the same on the site for everyone which means we can spend more time developing coolness and less time trying to keep the coolness from breaking other things on the site. Never perfect, but it's getting better.
Yeah, since I posted this morning, the empty line has disappeared for me, too, both in the OP and in posts I'm making. Using Chrome 15.0.874.106.
|
|
I think I found a bug in the forums.Testing since this has been happening to me as well. Single empty line entry coming.
Bam.
Double empty line entry:
Boom.
edit-happens with 10+ lines too.
Large amounts of empty lines were supposed to go away from the information I had. I'll take a look at it tomorrow and see if that's not supposed to be the case and I MIGHT have fixed something that was broken but that we used the broken bits and depended on them on the way there.
|
|
Also, I'm looking at this in FireFox 3.6.24, Chrome 15.0.874.106, Safari 5.1.1, and IE 8 and your first post looks the same as the pic you linked when you said it was fixed. And that's what it's supposed to look like, correct? It's also possible that something got a little wonky when we rolled the site last...
Also, I'm looking at this in FireFox 3.6.24, Chrome 15.0.874.106, Safari 5.1.1, and IE 8 and your first post looks the same as the pic you linked when you said it was fixed. And that's what it's supposed to look like, correct? It's also possible that something got a little wonky when we rolled the site last...
The 'fixed' pic is what it should look like (and still does, woot): a blank line between each line of text in my OP.
However, it seems like links inside quotes just broke.
I'll show it here using parens instead of square brackets. I'll quote you, and link to your post within the quote like thus:
(QUOTE="(URL=urlhere)Your Name(/URL)") quoted text (/QUOTE)
Which normally looks like:
Lissa Guillet (Assistant Software Developer) wrote:
purple box with quoted text.
Here's how it actually happens:
Also, I'm looking at this in FireFox
the quotes don't encapsulate the URL tags within the QUOTE header thing.
So many of my over-formatted posts are all borky now, because I tried to be fancy and have the QUOTE name be a link to the post I was quoting. (though, to be fair, it did work at the time).
This is happening in FF and Safari, so I think it's not an old-browser issue.
We'll take another look.
It doesn't get said enough, but You Guys Rule.
|
|
Also, I'm looking at this in FireFox 3.6.24, Chrome 15.0.874.106, Safari 5.1.1, and IE 8 and your first post looks the same as the pic you linked when you said it was fixed. And that's what it's supposed to look like, correct? It's also possible that something got a little wonky when we rolled the site last...The 'fixed' pic is what it should look like (and still does, woot): a blank line between each line of text in my OP.
However, it seems like links inside quotes just broke.
I'll show it here using parens instead of square brackets. I'll quote you, and link to your post within the quote like thus:
(QUOTE="(URL=urlhere)Your Name(/URL)") quoted text (/QUOTE)
Which normally looks like:
Lissa Guillet (Assistant Software Developer) wrote:
purple box with quoted text.Here's how it actually happens:
Also, I'm looking at this in FireFoxthe quotes don't encapsulate the URL tags within the QUOTE header thing.
So many of my over-formatted posts are all borky now, because I tried to be fancy and have the QUOTE name be a link to the post I was quoting. (though, to be fair, it did work at the time).
This is happening in FF and Safari, so I think it's not an old-browser issue.
No that's definitely happening server side and I think that should work reasonably. Let me see if I can figure out why that's getting all borked.
|
I still have problems with the empty lines.
They seem to be accepted at random or not accepted when you add to a previous post.
For example in this post there is a empty line before the Edit part.
The formatted text don't accept that and don't allow a separation between the edit part and the previously written part.
Edit (yes, I am doing it on purpose):
I am using Firefox (and here it accept the line separations).