Please see the attached files on this JIRA ticket for more info: http://issues.fluidproject.org/browse/FLUID-1986
On Fri, Jan 9, 2009 at 11:43 AM, Jacob Farber <[email protected]>wrote: > I didnt send these to the list the first time.... > > ---------- Forwarded message ---------- > From: Jacob Farber <[email protected]> > Date: Fri, Jan 9, 2009 at 11:03 AM > Subject: Re: Going on a Safari.... > To: Justin <[email protected]> > > > With the attached images you can see the fundamental differences. Please > bear in mind this is a bare bones approach with no effort to make the basic > button more attractive. > > Jacob > > On Fri, Jan 9, 2009 at 10:56 AM, Jacob Farber <[email protected] > > wrote: > >> +1 for documenting all these discrepencies in one place. >> >> The FSS CSS would normalize the appearance of the button everywhere in >> thedocument, not just UI Options.. >> >> Im prepping screenshots right now.... >> >> On Fri, Jan 9, 2009 at 10:39 AM, Justin <[email protected]> wrote: >> >>> In general I would agree that the font size would out weigh the merits of >>> the native appearance of the button. However, I have a question. >>> >>> I'm assuming that this solution would only solve the problem for the >>> button in the component, and that the other buttons the integrator puts on >>> the page would still suffer from this issue. >>> >>> In that case, would it be confusing to the integrator why it works in >>> some places and not in others? If this is a problem with the browser, it may >>> be a good idea to document the issue. >>> >>> In general, it may be helpful to have a section on the wiki or build site >>> that demonstrates all of the 3rd party issues that we have encountered and >>> are reliant on someone else to fix. (i.e. browser specific issues that don't >>> have a work around) This would also provide us with a point of reference to >>> determine if new browser versions solve these issues. >>> >>> Justin >>> On 9-Jan-09, at 9:41 AM, Anastasia Cheetham wrote: >>> >>> >>>> On 8-Jan-09, at 4:35 PM, Jacob Farber wrote: >>>> >>>> Do you think it's acceptable to squash the native appearance of a form >>>>> control in order to force it to accomodate other settings? Is it more >>>>> user-friendly for the font size to render properly or for the form control >>>>> to look like a native control? >>>>> >>>> >>>> Hm... This is an interesting question. >>>> >>>> First, I think a screen shot or two might help convey just what the >>>> button looks like when you do and don't do your proposed solution. >>>> >>>> My reaction is: I would think it would be better to sacrifice the native >>>> appearance in favor of a 'properly functioning' button. >>>> >>>> -- >>>> Anastasia Cheetham [email protected] >>>> Software Designer, Fluid Project http://fluidproject.org >>>> Adaptive Technology Resource Centre / University of Toronto >>>> >>>> _______________________________________________________ >>>> fluid-work mailing list - [email protected] >>>> To unsubscribe, change settings or access archives, >>>> see http://fluidproject.org/mailman/listinfo/fluid-work >>>> >>> >>> >> > >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
