darn YOUR EYES!
(Interestingly, what is written is not what is shown here...)
Heh, I know how that is. I spend hours updating my course material only to have a student spot a typo in the first 15 minutes of class. (Sigh.)
If you're doing cleanup, I could use the following:
1. Ensure that tooltips never contain the same kind of quote used in the title
attribute. While the Java library seems to deal with it okay somehow (?), a web browser won't. So if the final HTML will be <span title="...">
then the tooltip should only use single quotes, and a double quote should be represented as "
(I think that's the right one).
2. Set the nesting of HTML elements to be consistent. Again, this doesn't matter for the display in the chat window, but I'm interested in processing the chat log's HTML for display in a web browser. In this case, I'd like to be able to search for text by using the nested elements as a pattern, such as the CSS selector td b font span
. But the nesting is different in different places and that complicates things. Technically the title
attribute shouldn't contain <
, but <
. But man, that would look ugly!
3. As an alternative to #2, add a class
attribute on all <span>
elements to identify what it contains. I've noticed, for example, that the string "Primary Target:" of the attack field has a separate (but identical) tooltip as the actual attack output itself. This bulks up the HTML unnecessarily, but more importantly it means I can't just scan the HTML looking for title
attributes to identify pieces. If those elements had class
attributes I could scan for that and ignore everything else. I'm thinking of classes like class="player secret attack"
or class="gm secret skillcheck"
. It might be easiest to use player/gm and then the name of the macro that generated it. This would let me strip out GM tooltips that I don't want players to see when I post my chat log on a web site somewhere.
4. Only use an id
with a particular value once. There are spots in the Mod Report (I think) that contain <tr id="...">
where the id
can be duplicated, if not in the same mod report then in the next mod report when it gets printed. That's a no-no in HTML terms. If they were changed to class="..."
that would solve the validation error and could still be useful in other ways. (Note that having an id is not currently useful at all within MT.)
But I'll use whatever you put out! It's a great FW and saves me a huge amount of time
! Thanks, Lindsay!