Right now, Event title, note and location are TEXT fields. However, I'd like
them to be HTML fields for the following reasons:
- Ability to iclude links (to the web and to other events, see also bug 137777)
- Ability to 'customize' an event - with colors, images, header size,
paragraphs, and all the other nice HTML tags. this adds a LOT of usability, and
gives the user a lot more freedom about how he wants his events to be displayed.
- We're in Mozilla, and Mozilla supports HTML -> it might not be that hard to
get it interpreted.
- Go to day view and take a look at a 7 hour event. You see a lot of space used
by it, and only a tiny little event title on top. With HTML the user might
actually use that space for information rather than waste it.
- It might be THE advantage compared to Lotus and so on - the feature that
nobody else has.
I don't think there's such a thing as an HTML box in Mozilla, but I'll give you
the benefit of the doubt and just send this to nobody. I'm not going to be doing
I'll give it a try.
Here's a short status report... I tried to program a little over the weekend,
and that's what I could do:
- I can convert a string of text to a 'tree of objects' or however you wanna
call that. I'm using the 'range' command for that:
var HTMLText=range.createContextualFragment("<br><it>Hello, World!</it></br><br>
Dom Inspector shows that the HTML is parsed correctly.
- I can display HTML text inside an event box. I'm using the XUL browser object
(a read only iframe) to display html inside the box. If I construct the object,
add www.mozilla.org as src and attach it to the event box, I really get the
mozilla homepage inside the box.
-I can create an empty HTML broser (or iframe), and I have the DOM objects made
by my string, but I couldn't figure out how to transfer the DOM objects into the
browser at the right place (i.e. in browser->HTML->Body). I'm working on that
/* var eventHTMLBox=document.createElement("browser");
eventBox.appendChild( eventHTMLBox );
Finally the resolution would look like that: A preference somewhere to specify
if HTML events are allowed. If yes, there's a browser created for every event
box, and the event contents are added: first the title, then the location,
finally the description. All of them could themselves contain HTML tags.
May I assign this bug to myself? Or does anybody else want to experiment with that?
If HTML is used, the fields should also be stored in the iCalendar as plain
The iCalendar spec (ftp://ftp.isi.edu/in-notes/rfc2445.txt) has some
information about how to handle this, using an ALTREP parameter:
altrepparam = "ALTREP" "=" DQUOTE uri DQUOTE
Description: The parameter specifies a URI that points to an
alternate representation for a textual property value. A property
specifying this parameter MUST also include a value that reflects the
default representation of the text value. The individual URI
parameter values MUST each be specified in a quoted-string.
Don't know if this is still active...
the message composer and the web page composer do exactly what we want. maybe we
can reuse code from them?
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Please add my vote for this feature. Imagine a shared university course calendar
with all students subscribed. Each day contains a listing of classes (e.g.,
"Math 101, 10:00 - 11:30am"). Each class is a link to the home page for the
course. It would be a great feature for schools.
Please add my vote too. This is an extremely useful feature -- perhaps the most
important right now.
(In reply to comment #7)
> Please add my vote for this feature.
(In reply to comment #8)
> Please add my vote too.
You can vote on your own by using "Vote for this bug"
(In reply to comment #7)
> Imagine a shared university course
> with all students subscribed. Each day contains a listing of classes (e.g.,
> "Math 101, 10:00 - 11:30am"). Each class is a link to the home page for the
> course. It would be a great feature for schools.
This is already possible due to the URL field.
*** Bug 431337 has been marked as a duplicate of this bug. ***
*** Bug 552916 has been marked as a duplicate of this bug. ***
It would be nice to have an HTML editor like the one used by Thunderbird for email.
Markdown would also be a nice alternative, but perhaps too advanced.
I'd like to see the description field support html with a formatting tool bar of its own. Several years ago I read the book, "Take Back Your Life! Using Microsoft Office Outlook 2007 to get organized and stay organized" by McGhee and Wittry. That book shows how to use event descriptions for planning and accomplishing tasks. Because event descriptions are used extensively in that approach, formatting is used to highlight the different parts of a task. So, there's another reason for having this feature, though probably only a small fraction of users will use such a feature.
Bug 553132 would be a subset of this.
I'd propose to rename this to:
Task/Event descriptions/text should be HTML/rich text formatting
to make it easier to find.
Good idea. I had trouble finding it with the current name. (Looks like I don't have authority to rename it myself.)
*** Bug 1230145 has been marked as a duplicate of this bug. ***