Answered by:
FF3 + Forums compatibility: Code Preview

Question
-
I'm begining to like the look of the forum. have the borders of various things changed? It's looks a bit ore slick.
The code dialog:
- The Preview button is where Submit should be. Preview should be under the preview box.
- The Submit button is where Preview should be. The Preview is not submitted, the code is.
- The code is still not pre-selected for the forum.
Pressing submit with no title, blanks the Body.
--------------------------
Error Writeup, per Ed's Request
The awkward behaviour appears in FF 3.6.26. The recent 3.6.27 patch made it even worse. Hitting reply shows a reply box that either never allows entry (the page never stops loading, the "x" on the toolbar is continously active), or takes a significant aount of time. This seems intermittant, and reloading the page sometimes fixes the problem. If MS declares FF 3 unsupported, i won't be happy, but i'll understand.
- Moved by Naomi N Monday, February 13, 2012 5:24 PM More of a problem (From:Suggestions and Feedback for the Forums)
- Edited by Brian Tkatch Wednesday, February 22, 2012 1:09 PM
- The Preview button is where Submit should be. Preview should be under the preview box.
Answers
-
FF is one of the main browsers we use for testing, but about versions we generally use one of the latest like 9.0.1 so we are not doing a lot of testing on FF3
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, February 22, 2012 4:04 AM
- Marked as answer by Brian Tkatch Wednesday, February 22, 2012 1:09 PM
All replies
-
Pressing submit with no title, blanks the Body.
Thanks for your feedback. What browser are you using? When I try to submit without the title I get a message telling me the title must be 1 to 255 characters long and the text in the message body is kept.
-
FF3.2.26. It gives me the message to, but it also blanks the body.
Hitting edit after a reply is posted does the same thing. Perhaps they ar related. If the page is reloaded, the issue goes away.
- Edited by Brian Tkatch Tuesday, February 14, 2012 1:20 PM
-
blanks the body.
Hitting edit after a reply is posted does the same thing.
How are you composing? E.g. I have seen similar symptoms when replying with quotes to others' posts. E.g. the HTML source pane is blank and an Edit is blank. I think it is being caused by span tags from the pieces I am quoting. The presence of the span tags and other HTML would mean that the post I had quoted was not originally composed on this forum. E.g. someone had used another editor and pasted in their comment from it or at least had pasted some such HTML into their comments and editing with that had caused those discrepancies.
So, before you click Submit, see if you can use the HTML source pane to capture whatever it is that you are going to post. Then if you need to retry it you will at least be able to have something that you can try to edit in the retry's HTML source pane. This trick is also useful if you run into the case in which you are only given the option to post in plain text. In fact, then you need to provide some HTML (such as P and BR and BLOCKQUOTE if you are quoting) in order to make anything useful out of your typing.
FYI
Robert Aldwinckle
--- -
-
-
It''s good to know it was a design decision, whether we agree with it or not. :)
The code editor has you choose a language. Most forums center around one language, meaning, each and every time code is posted, the posters (in a given forum) choose the samer language. This seems redundant as an obvious default language can be used on a per forum basis.
For example, the SQL Server forums can use SQL, the VB/Access forums can use VB, etc. Each forum's administrator/moderator should be able to set a default language. As a default, it is still changeable by the poster for a particular post that uses another language.
This would save needless click and avert mistakes. As long as the default is per forum i can't imagine any downsides.
- Edited by Brian Tkatch Monday, February 20, 2012 4:03 AM
-
-
-
It''s good to know it was a design decision, whether we agree with it or not. :)
The code editor has you choose a language. Most forums center around one language, meaning, each and every time code is posted, the posters (in a given forum) choose the samer language. This seems redundant as an obvious default language can be used on a per forum basis.
For example, the SQL Server forums can use SQL, the VB/Access forums can use VB, etc. Each forum's administrator/moderator should be able to set a default language. As a default, it is still changeable by the poster for a particular post that uses another language.
This would save needless click and avert mistakes. As long as the default is per forum i can't imagine any downsides.
Ah! I get it now.
Was this ever promised? This seems more like a missing feature than a bug. Can you write it up in the Suggestions forum and add it to the feature request Wiki article on TechNet Wiki?
Thanks!
Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
- Edited by Ed Price - MSFTMicrosoft employee Monday, February 20, 2012 9:42 AM
-
1. To me the buttons also seem in the wrong place. I would prefer to have Submit button right bellow the pane where we enter the code.
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
Understood. To me it makes sense though (Insert button is at the right, next to the Cancel button). At this point, changing it seems like more of a request than fixing a bug, especially since it's part of the design.
Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
- Edited by Ed Price - MSFTMicrosoft employee Monday, February 20, 2012 9:45 AM
-
This is a very good suggestion. Say, in Transact-SQL forum 99% of the cases use sql for the language.
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
+1. Agreed; good feature request.Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
-
So it looks like #1-3 are all suggestions (which is where you posted this in the first place). We might just want to move this back, but it's really two different feature requests/suggestions... #1 moving the Preview and Insert buttons (your #1 and #2) and #2 pre-selecting the code option (your #3).
"Pressing submit with no title, blanks the Body." - This seems to be the only bug here. I assume you mean when asking a question, right?
Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
- Edited by Ed Price - MSFTMicrosoft employee Monday, February 20, 2012 7:33 PM
-
So it looks like #1-3 are all suggestions (which is where you posted this in the first place). We might just want to move this back, but it's really two different feature requests/suggestions... #1 moving the Preview and Insert buttons (your #1 and #2) and #2 pre-selecting the code option.
"Pressing submit with no title, blanks the Body." - This seems to be the only bug here. I assume you mean when asking a question, right?
Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
I can't repro and neither can Eduardo. What are the steps?
Thanks!
Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
-
Phew, lots of posts. I do love the reponses of the MS teams here. You and Brent stand out. I originally posted this as a comment about the design, that is, that i liked the boxes. As i posted the further suggestions my "grrrrrr!" got out, and it sounded more like a bug report. Until finally, the final line was a bug i noticed en route. Naomi saw the change in my atittude, and appropriately moved it. You noticed how i started. Sorry for the confusion. :)
The awkward behaviour appears in FF 3.6.26. The recent 3.6.27 patch made it even worse. Hitting reply shows a reply box that either never allows entry (the page never stops loading, the "x" on the toolbar is continously active), or takes a significant aount of time. This seems intermittant, and reloading the page sometimes fixes the problem. If MS declares FF 3 unsupported, i won't be happy, but i'll understand.
- Edited by Brian Tkatch Monday, February 20, 2012 1:30 PM
-
Hey would you mind changing your title and post to reflect that really this is a bug report about FF3 + Forums compatibility (and include your write up of the specifics)?
I know it didn't start as a bug, but that's where it ended up. =^)
Thanks!
Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
-
-
FF is one of the main browsers we use for testing, but about versions we generally use one of the latest like 9.0.1 so we are not doing a lot of testing on FF3
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, February 22, 2012 4:04 AM
- Marked as answer by Brian Tkatch Wednesday, February 22, 2012 1:09 PM
-
FF is one of the main browsers we use for testing, but about versions we generally use one of the latest like 9.0.1 so we are not doing a lot of testing on FF3
So, Brian, are you able to upgrade your FF (or use another recent browser)?
Thanks!
Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)
-
I'm able to, but i won't.
FF4 wasn't the best, and i don't like the direction they have taken FF in. Those all-too-often updates are very annoying, and, please excuse me, the Win 7 style menu bar is annoying. As one of those people who primarily use the keyboard, a textual menu bar is what i want.
FF used to have its own flavor. FF3 with Old Location Bar (getting rid of that annoying "awesomebar") is where i'm at. I'll probably have to switch at some point, but i doubt it will be to another version of FF.
So, i have to accept problems like this. I guess the question is, should i report them?
Oh, and FF 3.6.27, was just released. So, it qualifies as recent. Just not the "latest". With Chrome and FF, version numbers have ceased to mean anything.
- Edited by Brian Tkatch Wednesday, February 22, 2012 1:11 PM