Inline Edit: Blanks -- initial, embedded, and trailing

[Paul Zablosky]

It's interesting that a lot of the tricky issues with Inline Edit are 
associated with "whitespace" -- blanks, tabs, newlines, and 
"emptiness".  Here it's a case of the user having to deal with the 
/internal /value of the string (which may contain repeated spaces) while 
editing, and later seeing the /display/ value which has been filtered 
through HTML.  If the user is used to doing markup-language text 
editing, they probably understand what is going on. If they're used to 
WYSIWYG, they probably don't.

Paul

Anastasia Cheetham wrote:
>
> On 21-Jul-08, at 8:05 PM, Paul Zablosky wrote:
>
>> A couple of questions:
>>     • Is the trimming and compressing of blanks part of the intended 
>> behaviour of the component?
>
> The compression of blanks is a side effect of the way HTML works - if 
> you put a string of spaces into HTML markup, they are displayed as a 
> single space. If you want what is called a 'non-breaking space,' you 
> have to use the special character ' ' instead of a regular space 
> character.
>
> It's a question for the designers as to what would be the ideal 
> behaviour when a user enters a string of spaces into the edit field.
>
>>     • Shouldn't the width of the edit box be the same as the editable 
>> text width?
>
> This is a good question - another one for the designers, I suspect :-)
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080722/a43865e5/attachment.html>