[crossfire] Feature proposition: [img] tag

[Mark Wedel]

Nicolas Weeger wrote:
>>   More likely want to have something like an img tag with hints, for things
>> like popup, desired size, etc.
> 
> Then let's do the whole trick and use some XHTML subset?
> 
> 
>>   Note that anything that deals with popups can be annoying in some areas. 
>> If you read some scroll and it suddenly popped up a window, I'm not sure
>> I'd like that.  It'd probably be better as a default for the message to
>> just be displayed, something like 'This scroll contains a map.  Click on
>> map image for a larger view (small map image displayed)'
> 
> Client-side issue.
> 
> 
> My opinion: let's implement the tag in basic form, use it, and adjust later if 
> needed.

  Fair enough.  I think my point may be more that the spec (for lack of better 
work) should be aware we may want to add extra specifiers, and while they client 
has not requirement to handle them (since we don't know what they are), it 
shouldn't suddenly break if they show up.

  It could otherwise be a real pain if we decide we want to add something like 
[img popup=1], and the client is only looking for [img] and suddenly doesn't 
work right.

  So in that case, an old client would still recognize that as a valid img tag - 
it wouldn't know what that popup=1 thing means, but would display the image just 
like it always had.