Tags are not always wrapped in markup in Task.content

Reported by Kevin Mehall on 2010-01-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Getting Things GNOME!
Low
Unassigned

Bug Description

Normally, tags in a task's content attribute are represented by e.g. "<tag>@name</tag>", but in certain cases the XML markup is not present. Sometimes the editor loses the markup when it is closed and triggers a save.

I'm trying make the lp:~gtg-user/gtg/gmail-like-ui branch not show tag names in the preview text. Yes, I know I could use a regexp to delete bare @tag strings instead, but it would be nice if the representation were consistent.

One scenario to reproduce:
 1. Create a new task and give it a title
 2. Add "@tag1 @tag2" on the first line
 3. Add any non-tag text to the next line
 4. Close the task editor
 5. Open the editor again
 6. Modify the last line of text
 7. Close the task editor (the markup only disappears upon task editor close)

Kevin Mehall (kevin-mehall) wrote :

I'm also wondering about the necessity of storing the markup. The editor already re-scans and re-generates it when it is opened. The only case where it stores additional data is for subtasks, where it holds the task ID.

Changed in gtg:
status: New → Confirmed
importance: Undecided → Low
milestone: none → 0.3
Izidor Matušov (izidor) on 2011-08-12
tags: added: editor taskeditor ui
Izidor Matušov (izidor) wrote :

Note: The markup can be checked by watching task XML.

Changed in gtg:
milestone: 0.3 → 0.3.2
Izidor Matušov (izidor) on 2012-07-18
Changed in gtg:
milestone: 0.3.2 → 0.4
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers