|
|
 top
|
  Subject: Re: Default preview mode and debugging in 3.1.59a
Author: Minollo I.
Date: 05 Sep 2001 02:40 PM
|
>1. Browser preview doesn't seem to correctly default to an HTML view (and
>instead defaults to XML) when using an external XSLT engine (Xalan 2.1) on
>an XSL that has output starting with an html tag. The XSLT engine
>correctly defaults to HTML (indicated by the fact that an additional
>content-type META tag is generated) but the XSLT preview fails because it
>tries to render as XML and it isn't well formed (the META tag isn't
>closed). The workaround is to define xsl:output method="html" once, and
>then all future previews (even if the xsl:output is removed) default
>correctly to HTML. The failure recurs when StylusStudio is restarted.
I understand. The problem here is that when an output method is not
specified, the processor automatically switches to HTML or XML output
depending on the result of the processing (according to the XSLT 1.0
specs). When the preview happens using the internal processor, the
processor lets us know what's the "final" chosen output handler. When the
processing is external, we don't have such feedback, and we default to XML.
A reasonable solution would probably be to take a look at the result and
understand what kind of output has been generated. We'll think about that.
>2. It was great that 3.1.59a fixed the window repositioning that occurred
>in 57 when stepping through an XSLT in debug mode. However, I would be
>even more happy if the window didn't left justify on each step. Any
>chance there is a quorum that would like it to be extended to just move
>the yellow arrow in the margin and advance lines when necessary, but not
>adjust the horizontal view?
I don't have strong feelings about that. The other debuggers (not only
XSLT) that I know have the same behavior Stylus Studio has.
>P.S. I haven't been able to recreate the strange Watch Window behavior I
>reported before, so I guess that will have to be chalked up as an
>unexplainable phenomenon. I'll remember to do screen captures next time :)
If you were having problems with column sizing in the Watch window, that
might have been caused by some older version of Stylus Studio that you run;
Stylus Studio saves the proportions between the two columns, and re-applies
them when the window is created. In older releases of Stylus Studio, there
was a bug which caused one of the two columns to be sized to 100% of the
window width (even if it was hidden), and that information might have been
stored in the registry and re-used when you saw the problem.
That's my best guess on what might have happened.
Thanks for the feedback,
Minollo
|
|
|
|
next