July 5, 2009 at 11:32 am
The code windows in use on SSC behave differently depending on the browser being used to view the page.
These problems really need to be fixed across all platforms.
Some recent problems:
1. XML - XML code is dropped from code windows (see this post for an example) (Note that if you press the "Quote" button for this message, you can see the entered xml text!).
2. XML - XML elements are mangled in code windows - as in some browsers see incorrect text. This is causing confusion between posters. See this post for an example.
This is a good example:
Press the "Quote" button to see that the tags were actually entered the way the text specifies--- but the code window doesn't show it (In FireFox, they are all showing as lower case; in IE they all show as upper case). Since XML is case sensitive, this is a pretty big issue.
3. SQL Code - there have been many documented issues with sql code. See this post for a summary.
In short, the code windows are causing a problem, and they need to be fixed.
Thanks,
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
July 5, 2009 at 1:35 pm
Very cool... I'm not the only one having such problems. Thanks for posting this, Wayne. If we can get enough other people to document the problems, maybe they'll finally fix them. I've shown them many such problems especially where IE is concerned. Although they claim it's fixed, nearly all the problems I documented still remain as problems.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2009 at 4:15 pm
Here's some "evidence of confusion" to support the need for fixing the issue (based on IE 6.0.2900.5512):
http://www.sqlservercentral.com/Forums/FindPost742192.aspx -> confusion caused
http://www.sqlservercentral.com/Forums/FindPost742141.aspx -> wrong color coding due to /* using XQuery
http://www.sqlservercentral.com/Forums/FindPost733805.aspx -> using the original tags defined by the OP but wrong display.
July 5, 2009 at 9:33 pm
@Lutz: Thanks for the additional links.
What brought this to a head for me was that I was contacted by three senior posters (senior, by my definition, being > 1000 points) this weekend about some XML code that I had posted (in two separate threads) not working. In one instance, the case of the provided code had changed (on his browser, it was showing as upper case), making the statement not work. In another instance, all of the xml code within tags was missing, but the statement would run - and produce nothing.
If senior posters here are getting caught up in all of this confusion, just imagine how the novices are. And it's not like these issues hasn't been brought up before... I run into posts periodically mentioning various issues about the code windows, and how they've been reported.
Just today I ran into a variation of the code block that I hadn't seen before ... using (code="XML") instead of just (code) (replace parenthesis with brackets). This variation isn't listed on the "IFCode" link, so how are we supposed to know to use it? Are there other variations that we should know about?
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
July 5, 2009 at 9:44 pm
Wayne,
Sorry, I need to update the IFCode, and I'll do that tomorrow. The code formatting has been a challenge, and it's confusing to everyone. I wish there were a better solution, and I'm hoping we'll get one working before too much longer.
July 6, 2009 at 12:19 pm
Please drop examples of issues in here. It's not that we don't want to fix this, but it's a complicated problem, especially when trying to render different types of code in different ways. Add to that the fact different browsers display things differently, and it's an issue.
We have gotten dedicated resources, finally after some time, and they are working on changes. A cut/paste to SSMS should go live this weekend, and that will fix some things.
July 6, 2009 at 2:04 pm
Glad to know it's being worked on.
I've had problems with the XML capitalization issue. Interestingly enough, it used to capitalize everything, but the sample posted earlier in this thread was all lowercase. Or maybe it does some one way and others another way, I haven't taken the time to really analyze the cases for a pattern.
My main beef with the main code window is the way it mangles tab indents when I copy-and-paste from SSMS.
The double-lines thing when I copy to SSMS is mildly annoying, but the indent thing matters much more to me. Makes the code nearly unreadable in many cases.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 6, 2009 at 2:11 pm
Phil Factor is constantly complaining about this as well. I heard a fix is in for a Sat deployment, but we'll see.
July 6, 2009 at 7:00 pm
Steve Jones - Editor (7/6/2009)
Please drop examples of issues in here.
Steve,
I can read this two different ways, and I can't tell which way you mean:
1. Post all examples of the issue in this thread.
2. Stop posting examples of the issue.
Would you clarify please?
Thanks,
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
July 8, 2009 at 4:45 am
Possible issues with Google Chrome?
http://www.sqlservercentral.com/Forums/FindPost749128.aspx
____________________________________________________
Deja View - The strange feeling that somewhere, sometime you've optimised this query before
How to get the best help on a forum
http://www.sqlservercentral.com/articles/Best+Practices/61537July 8, 2009 at 8:53 am
Post examples/links in here.
The more examples we can pass to the devs, the better.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply