I've made a minor change which *fixes* both these problems. OK, well not completely but it makes it better. All I really did was change the tag for the editable element from an h4 to a span. An h4 is a block element which by definition is width: 100%.
I changed the styling ever so slightly adding a faint border to .invitation. - Eli On Jun 18, 2008, at 8:34 AM, Eli Cochran wrote: > I'm going to play around with this a bit this morning. A good > distraction from a tetchy tummy. > > - Eli > > On Jun 18, 2008, at 7:53 AM, Eli Cochran wrote: > >> I agree that the column resizing is annoying but I played around >> with the styling and the HTML and I have to say, it's not easy to >> fix. >> >> The two choices to fix it are: >> - having the edit box be only as wide as the original text which >> makes it more difficult for the user to add more characters to the >> field, or to even know that they can add more text than is there. >> - constraining the widths of the table column on the fly. Now that >> might work. It would be a "special case" since an inline editor >> wouldn't always be in a table. The bigger issue is that >> constraining column widths in tables is notoriously hard to do in a >> nice way. Hmm... >> >> That's definitely a tough one. >> >> - Eli >> >> On Jun 18, 2008, at 7:35 AM, erin yu wrote: >> >>> Two little bugs :) >>> >>> 1. I think the yellow highlight should highlight the editable text >>> only and shouldn't go all the way to the end of the column. This >>> convention is useful esp. when not the entire text in the column is >>> editable. I'll open a JIRA for it if everyone agrees. >>> 2. When you click on the yellow highlight, the subject becomes an >>> editable text box _and_ at the same time expands the column. As a >>> results, the other columns to the right of the subject column are >>> shifted to the right. Will open a JIRA for it. >>> >>> Erin >>> >>> >>> On 18-Jun-08, at 10:13 AM, Michelle D'Souza wrote: >>> >>>> Hi everyone, >>>> >>>> We are planning to cut an 0.4 beta on June 26th. In it we'd like to >>>> feature both Inline Edit and Pager in preview modes. To accomplish >>>> this, I would like to switch my attention from Inline Edit to Pager >>>> even though Inline Edit is still in basic form. Designers, can you >>>> take a look at Inline Edit and see what you think? Presenters, is >>>> there enough done of Inline Edit for your presentations? >>>> >>>> http://build.fluidproject.org/fluid/sample-code/inline-edit/ >>>> announcements/announcements.html >>>> >>>> Thanks, >>>> >>>> Michelle >>>> >>>> ------------------------------------------------------ >>>> Michelle D'Souza >>>> Software Developer, Fluid Project >>>> Adaptive Technology Resource Centre >>>> University of Toronto >>>> >>>> >>>> >>>> _______________________________________________ >>>> fluid-work mailing list >>>> [email protected] >>>> http://fluidproject.org/mailman/listinfo/fluid-work >>> >>> _______________________________________________ >>> fluid-work mailing list >>> [email protected] >>> http://fluidproject.org/mailman/listinfo/fluid-work >> >> . . . . . . . . . . . . . . . . . . >> . >> >> Eli Cochran >> user interaction developer >> ETS, UC Berkeley >> >> > > . . . . . . . . . . . . . . . . . . > . > > Eli Cochran > user interaction developer > ETS, UC Berkeley > > . . . . . . . . . . . . . . . . . . . Eli Cochran user interaction developer ETS, UC Berkeley _______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
