Cross-browser nuances
s@rdalya's behaviors may slightly differ on different platforms.
These nuances and possible resolutions to them (if any) are maintained in this page.
In addition several API-specific details are listed in this page as well.
Several exceptional situations are given here as well.
Note that the issues listed in this page are not bugs actually. They may or may not be fixed in the forecoming versions of s@rdalya. If you have any workaround, feel free to share it.
Elements without and ID.
If an element on the page does not have an id, certain s@rdalya objects, like DraggableLayer may not function properly on that element.
So, if you attach an object to DraggableLayer, make sure that it has an id.
Or give it an explicit id via DOM scripting.
For example:
var lyr=document.getElementsByTagName("p")[0];
lyr.id="ParaDrag";
new DraggableLayer(lyr).fixToDragMode();
EventHandler registers a separate event whenever addEventListener method is called for Internet Explorer. However it should register an event only once if the function is identical. The behavior in other browsers (Mozilla, Netscape, Opera) are as expected.
That is
eh.addEventListener("btnX","click",fn);
eh.addEventListener("btnX","click",fn);
will trigger fn00 twice when clicked to "btnX" in IE. In Mozilla, Netscape and Opera, fn** will be called only once.
top left coordinates and Opera
If you don't explicitly specify the top and left values of a layer for the page; Opera will assume the layer is placed relative to the top-left corner of the browser window. However, it should have been positioned relative to its relatively positioned container according to W3C specs.
Some CSS values may return "" although they are not.
For Mozilla 1.5 and Netscape8 Beta; StyleManager returns "" for borderColor and borderWidth CSS values, regardless of what they have been defined in the CSS.
There are differences between the default values StyleManager returns for Internet Explorer and Mozilla or Opera.
Internet Explorer:
visibility: visible => isVisible == true
top : auto => getTop == NaN
left : auto => getLeft == NaN
Mozilla-based browsers & Opera:
visibility: inherit => isVisible == false
top : 0px => getTop == 0px
left : 0px => getLeft == 0px
Therefore visibility, top and left CSS values should be given explicitly in the CSS
file if they are needed to be recalled later.
Usage of more than one ToolTip objects.
If there are more than one ToolTip objects in a document,
only the last one is used.
Thus, it is not practical to use more than one ToolTip per page.
Differences between DynamicLayer and StyleManager on retrieving dimensions.
DynamicLayer's (set/get)Width, (set/get)Height methods include paddings and borders in their calculations as well.
However, StyleManager does not include paddings and borders in calculation.
Thus, the findings of these objects may differ.
Opera and keyboard shortcuts
Opera defines tons of shortcut keys for the keyboard. Therefore switching from drag mode to resize mode in a DraggableLayer may occasionally result in slight render anomalies.
However the behavior is not permanent: The view will recover when the resize operation finishes. This problem is related to the special key assignment of Opera; if you have not pressed any special key, you will not encounter the problem anyway.
Comments (0)
You don't have permission to comment on this page.