Last Updated: 11 Feb 2016 13:53 by ADMIN
Marin Bratanov
Created on: 29 Jan 2016 12:18
Category: Splitter
Type: Bug Report
Sliding zone tabs text is upside down in Firefox
Potential workaround is attached but it requires modification of the markup to add a class to the pane that holds the vertical sliding zone as well. If you do not need this fixed urgently, wait for an official fix.
Marin Bratanov
Posted on: 05 Feb 2016 14:44
This issue is in our backlog with very high priority and it is very likely that a fix will be available in Q1 2016 SP1.
Posted on: 05 Feb 2016 13:58
Thank you for your responsiveness.  I would like to add in that this is currently affecting our products as well and we would like to up-vote a fix for an upcoming release.  We attempted to apply the workaround, and in our case the end result looked worse than the upside down text, so we will not be deploying that.
Marin Bratanov
Posted on: 05 Feb 2016 12:49
As I explained, browsers change. This prompts changes in our controls as well. When a browser suddenly starts supporting a CSS rule it did not support before, such things can happen, This is why older versions may have more issues than the current ones - the browser versions they were written against were even older and had even less support for such rules.

As for the other post - while this is not the correct place to discuss this, I will offer some answers:
- FF64bit was NOT mainstream in 2011, nor was it supported
- RadTextbox has improved a great deal and uses less elements. The Lightweight RenderMode aims at that precise thing. Out of those listed there - the span is needed for some features (as is a lot of HTML you may find useless at first glance). One of the inputs is something EVERY MS AJAX-based control will have. Out of the other two one is no longer present.
- traditional JS does not work - this is expected, MS AJAX-based controls provide their own client-side API and DOM operations should rarely be used for them.

The same goes for all his other "issues".
Ultimately, the UI for ASP.NET AJAX controls are:
- based on the WebForms paradigm
- based on MS AJAX
This puts them in a very special position where they have a number of complications inherited from the framework.
Posted on: 05 Feb 2016 12:33
Thank you for confirming that Telerik controls are an accident waiting to happen, with little recourse short of a) paying the annual subscription and praying for a real fix b)moving to html controls and doing things with a solid architecture.  After quite a few years of arm wrestling with radcontrols, I have to agree fully with Deep Shah's blog at  Btw, with version 2014.2.618.40, the slidingpane breaks in all browsers and your solution did nothing.  A rule helped (.rspRotatedTabText {transform: rotate(180deg) !important;
font-size:9pt !important;}) but not with multiple slidingpanes in the same zone.

Marin Bratanov
Posted on: 01 Feb 2016 07:40
Hello Mark,

Sometimes browser updates can cause problems like that. Rules and properties that were not previously supported start working and this layers more transformations than needed in this case. We cannot know what the next browser version is going to bring and this is why we have frequent releases.
I can assure you this issue has high priority in our backlog.
I would also appreciate it if we could keep our tone civil.

Marin Bratanov
Posted on: 29 Jan 2016 17:29
Started happening out of the blue in Chrome and Firefox.  Amazing.  How could one NOT need it urgently???????????????   You believe providing users with upside down text is an OK thing to do????  Do you often visit Alice in Wonderland???