It's been awhile on htmlarea. My interest was more around the CSS issue in 
general HTML where IE was barfing. I will look at what you did in the new 
htmlarea for some clues I think.

Thanks,
Joseph

On 9/9/05, Robert Zeigler <[EMAIL PROTECTED]> wrote:
> 
> Joseph, when did you dl htmlarea? I uploaded a revised version
> (the version Patrick mentions here) on August 27th.
> 
> Robert
> 
> Patrick Casey wrote:
> > Robert sent me an email last week (for testing) with some updated
> > .css that looked a lot better (it's not perfect, but it's a *lot* 
> better). I
> > dunno if he's still playing with it in the hope of making it perfect, or 
> if
> > he's going to repackage it as is.
> >
> > Either way, he's definitely making progress, but you'll need to
> > touch base with him to see when (or if) a new version is coming out.
> >
> > --- Pat
> >
> >
> >>-----Original Message-----
> >>From: Joseph Hannon [mailto:[EMAIL PROTECTED]
> >>Sent: Friday, September 09, 2005 8:53 AM
> >>To: Tapestry users
> >>Subject: Re: One more HTML Area Question
> >>
> >>Pat,
> >>
> >>Any success on this CSS issue? I am experiencing the same type of thing
> >>using Tapestry 3.0.3, Firefox and IE. I am using XHTML and do have the
> >>XHTML
> >>DOCTYPE showing at the top of my html rendered source.
> >>
> >>Thanks,
> >>Joseph
> >>
> >>On 8/26/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
> >>
> >>>
> >>>I've got the world's simplest page for debugging purposes:
> >>>
> >>><span jwcid="@Body">
> >>><form jwcid="@Form">
> >>><span jwcid="@htmlarea:HtmlArea"
> >>>value="ognl:visit.currentUser.firstName" rows="12" cols="80"/>
> >>></form>
> >>></span>
> >>>
> >>>It draws perfectly on firefox (PM me if you want a screenie).
> >>>
> >>>On IE though, it draws as though none of the .css is being followed.
> >>>The buttonbars all have white backgrounds instead of BtnFace. All the
> >>>buttons are enabled all the time (even the ones that don't apply), the
> >>>text
> >>>area itself isn't bordered by a black line, and the edit area itself
> >>>default
> >>>to (and is stuck in) double space.
> >>>
> >>>It really smells like the .css isn't being loaded properly, but I
> >>>don't understand this implementation well enough to fix the problem.
> >>>
> >>>In fact, I can pretty much guarantee that it's a css loading problem
> >>>because if I inline the contents of htmlarea.css (from the jar file),
> >>
> >>the
> >>
> >>>page renders perfectly in IE and in Firefox. In other words if I copy
> >>
> >>the
> >>
> >>>.css contents and paste them into the head of the page inside of 
> <style>
> >>>tag
> >>>on my .html file, it draws properly (although IE still wants to double
> >>>space
> >>>everything).
> >>>
> >>>So I *think* we're dealing with an inability of the component to
> >>>load its .css properly. But, again, I'm stumped as to how to resolve 
> the
> >>>issue.
> >>>
> >>>Any suggestions?
> >>>
> >>>--- Pat
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Patrick Casey [mailto:[EMAIL PROTECTED]
> >>>>Sent: Friday, August 26, 2005 12:14 PM
> >>>>To: 'Tapestry users'
> >>>>Subject: RE: One more HTML Area Question
> >>>>
> >>>>
> >>>>I think it was actually a cache issue of some sort. After flushing
> >>>>my cache and restarting tomcat, rows, cols, and the tableOperations
> >>
> >>flag
> >>
> >>>>seem to be working just fine now. I think I'm running into some sort
> >>
> >>of
> >>
> >>>>CSS
> >>>>issue on IE though atm as the editor shows up w/o the grey background
> >>
> >>on
> >>
> >>>>the
> >>>>toolbars and w/o a frame around the editable area on IE, but shows up
> >>>
> >>>just
> >>>
> >>>>fine under gecko.
> >>>>
> >>>>I'm gonna bang on that for a bit and see if I can figure out what's
> >>>>afoot with the demon IE.
> >>>>
> >>>>Thanks for all the help,
> >>>>
> >>>>--- Pat
> >>>
> >>>
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Reply via email to