Dear Akkana (and Editor engineers),
I don't understand your term "output html". After performing these
actions starting with a blank file, the only option is to either "Save"
or "Save as" and in both cases, for me at least with Windows 2000112908,
the spaces appear in the saved file.
Furthermore, the spaces appear irrespective of any file save actions by
using the "View HTML Source" command. That command, it seems, uses the
serializer, and then converts the results back as if reading a file when
you return to Normal Edit mode - so View HTML Source is not to be
trusted as showing what is actually in Composer's internal data
structure. It typically changes the contents and perhaps structure of
the internal data too.
Bug 61288 reports a behaviour which I initially thought resulted from
one or perhaps two problems with particular parts of Composer - or more
likely with the interactions between various subsystems, each of which
looks OK on its own.
Now I think that there are so many causes of whitespace problems that I
can't pursue the matter any more. I reported this copy and paste
problem under this bug because it creates whitespace. This problem may
reflect one more underlying bug in addition to those which cause the
other problems.
Joe Francis is planning a major rewrite of the edit function, to deal
with whitespace at that time with the knowledge of where the various
bits of whitespace came from - rather than in a post-edit cleanup. This
is clearly the best approach - but I suspect that there are a number of
other problems regarding whitespace which could be cleared up first,
without great effort. I imagine that clearing them up would make
debugging all other whitespace problems a lot easier.
If this bug of whitespaces in copy and space can be shown to have a
distinct cause, then maybe it would be good to create a separate bug for
it - but by then it may be solved.
Cheers
- Robin
> Interestingly, these spaces do NOT appear when you do "output html".
> So evidently it has something to do with flags in the serializer (and
> also, we are no longer sending the same thing in Output HTML as we
> do in Save As, which is also a problem).
>
> Do we have a bug on this yet, or is it thought to be the same issue
> as Robin's other bug (61288), which sounds different to me?
>
> ...Akkana
