cannot remove bullets once added

Bug #101267 reported by Simeon Scott
4
Affects Status Importance Assigned to Milestone
Silva
Fix Released
Medium
Unassigned

Bug Description

A line with both bullets and subheading style in a document would not allow
removal of bullets. Pressing the bullet button in kupu simply added a *second*
bullet to the line. Forms editor did not seem to correctly display structure, or
else I didn't understand it (haven't used it much for a while).
Unfortunately I no longer have the problem doc saved, and could not reproduce
the problem from scratch.

Revision history for this message
Guido Wesdorp (guido-infrae) wrote :

I tried reproducing this, but it worked for me. However, I can imagine this sort
of thing can go wrong under certain circumstances or in certain browsers,
perhaps you can give a bit more information about the browser and OS you're
using, and how exactly to reproduce it?
If we find this to be a bug indeed, I think it will be quite hard to fix still,
since it would be a problem with some functionality offered by the browser
rather then in our own code: Kupu uses built-in browser functions to manage lists.
By the way, I was wondering what the result would be of placing your cursor on
the first character of the line and pressing backspace? Iirc that should remove
the bullet too...

Revision history for this message
Simeon Scott (simmo) wrote :

Guido,

As I noted, I was also unable to reproduce it once I had deleted the
relevent part of the doc .. which was before I logged the problem.

I was using Firefox PR1.0 and the problem occured in text which I had
copy-and-pasted from another kupu editor window. I don't know if it
occured straight away or a while later, but it persisted for a number of
sessions, so I deleted the lines and re-typed them.

Simeon

On Mon, Nov 08, 2004 at 11:47:52AM +0000, Guido Wesdorp wrote:
>
> Guido Wesdorp <email address hidden> added the comment:
>
> I tried reproducing this, but it worked for me. However, I can imagine this sort
> of thing can go wrong under certain circumstances or in certain browsers,
> perhaps you can give a bit more information about the browser and OS you're
> using, and how exactly to reproduce it?
> If we find this to be a bug indeed, I think it will be quite hard to fix still,
> since it would be a problem with some functionality offered by the browser
> rather then in our own code: Kupu uses built-in browser functions to manage lists.
> By the way, I was wondering what the result would be of placing your cursor on
> the first character of the line and pressing backspace? Iirc that should remove
> the bullet too...
>
> ----------
> nosy: +johnny
> status: unread -> chatting
>
> _____________________________________________
> Silva issue tracker <email address hidden>
> <http://issues.infrae.com/silva/issue1152>
> _____________________________________________

Revision history for this message
Simeon Scott (simmo) wrote :

found this happens quite frequently when trying things like nested lists,
multi-line list elements etc in kupu.

workaround is to save, fiddle with list again, save, repeat until it works
properly (3 or so times usually)

Revision history for this message
Simeon Scott (simmo) wrote :

other obviously related wierdnesses exist, eg see bug 1156 "images within list
elements show in kupu editor, but not in forms/preview/public preview" reported
by me

If trying to conjoin a line into a list, from being after (seperate from) the
list, things get wierd. Saving, reediting etc as suggested earlier fixes this.
Does not fix the images disappearing case.

Revision history for this message
Guido Wesdorp (guido-infrae) wrote :

Not quite happy with it, since this sort of stuff points to problems in the
transformations, which are currently not as good as they can be* and pretty hard
to read, but I'll check it out anyway. Thanks for the better description about
how to reproduce it.

* I feel like I'm repeating myself... there's a *lot* of code in Kupu as well as
Kupu-related code in Silva, and even though a lot of time has been spent to get
it working it's still far from flawless, I reckon it will take some tweaking and
perhaps even some rewriting to get it all in tip-top shape.

Revision history for this message
Guido Wesdorp (guido-infrae) wrote :

(In case that wasn't clear already: the 'not quite happy with it' part was a
joke, it's true that I don't like hacking those transformations, but obviously
it's not as bad as it sounded... ;)

Revision history for this message
Simeon Scott (simmo) wrote :

Guido,

Yes, I imagined most of the problems I encountered with various list
operations might be related, so I took the time to log each problem. :)

As Clemens pointed out, complex definition lists may be outside the
scope of Silva, I can live with that, but it would mean I would tend to
avoid the use of definition lists at all, for consistency of appearance
in the document.

Simeon

On Wed, Nov 17, 2004 at 11:24:05AM +0000, Guido Wesdorp wrote:
>
> Guido Wesdorp <email address hidden> added the comment:
>
> (In case that wasn't clear already: the 'not quite happy with it' part was a
> joke, it's true that I don't like hacking those transformations, but obviously
> it's not as bad as it sounded... ;)
>
> _____________________________________________
> Silva issue tracker <email address hidden>
> <http://issues.infrae.com/silva/issue1152>
> _____________________________________________

Revision history for this message
Guido Wesdorp (guido-infrae) wrote :

> but it would mean I would tend to
> avoid the use of definition lists at all, for consistency of appearance
> in the document.

I can imagine, I'll talk to the people that 'guard' the XML schema if we want to
allow complex dls.

Revision history for this message
Wim Boucquaert (wim-boucquaert) wrote :

List items shouldn't get any heading styling or layout also this raises an error message/warning when you try to do this now.

Changed in silva:
status: Confirmed → Fix Committed
Changed in silva:
milestone: none → 2.0.6
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.