PROTECTED]
Sent: Monday, August 27, 2007 8:48 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
A JIRA issue + a patch would make it more likely. :)
-- Adam
On 8/27/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote:
Can this be expected in 1.0.3?
Nate Perkins
480-441-3667
are not an intended recipient, please contact
the sender by reply email and
destroy all copies of the original message.
-Original Message-
From: Adam Winer [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 8:00 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
I'm
[mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 8:00 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
I'm getting the feeling that we really need to add a flag
to at least trh:html or both trh:html and tr:document
that supports forcing quirks mode.
Thoughts
by reply email and
destroy all copies of the original message.
From: Simon Lessard [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 8:21 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
Hello Nate
[mailto: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ]
Sent: Thursday, August 23, 2007 8:21 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
Hello Nate,
So what you're saying is that your
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
If you remove the doctype-root-element, doctype-system,
and doctype-public off of jsp:output, does the problem
go away? It looks as though that doctype is getting
pushed straight into the content stream. There's code
message.
-Original Message-
From: Adam Winer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 22, 2007 1:35 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
On 8/22/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote:
Hi,
I'm testing my project with 1.0.2
23, 2007 8:03 AM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2
I commented out the jsp:output and that fixed the problem.
Unfortunately I can not live with that solution as it is mandatory for
my project's pages. We have a requirement for a fixed bar on top and on
bottom
are not an intended recipient, please contact
the sender by reply email and
destroy all copies of the original message.
-Original Message-
From: Adam Winer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 22, 2007 10:57 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
.
From: Simon Lessard [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 8:21 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
Hello Nate,
So what you're saying is that your application will only ever work in
quirk mode? There's always a solution
by reply email and
destroy all copies of the original message.
From: Simon Lessard [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 8:21 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
Hello Nate,
So what you're saying
by reply email and
destroy all copies of the original message.
-Original Message-
From: Andrew Robinson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 8:48 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
You can use IE6 in quirks mode and firefox in standards
Probably, I am just using tr:document, so that is what I customized.
1.0.2 is working fine with PPR on firefox 2.0 and IE7 for me. I only
implemented the hack as I also wanted quirks mode functionality
for IE since IE7 has bugs/shortcomings with height percentage
allocations in standards mode.
That's a nice hack too imho as you can easily remove it once IE 6
disappears. And yeah it would also work for trh:head renderer.
On 8/23/07, Andrew Robinson [EMAIL PROTECTED] wrote:
Probably, I am just using tr:document, so that is what I customized.
1.0.2 is working fine with PPR on firefox
Nah, I mean if Nate was to use it.
In your case, Andrew, you might be able to remove it with MSIE 15 in 2030.
On the bright side, I don't know its validity, but you can use
http://www.w3schools.com/browsers/browsers_stats.asp to comfort yourself.
Regards,
~ Simon
On 8/23/07, Andrew Robinson
In your case, Andrew, you might be able to remove it with MSIE 15 in 2030.
I doubt that the number is higher than 8 in that year
On the bright side, I don't know its validity, but you can use
http://www.w3schools.com/browsers/browsers_stats.asp to
comfort yourself.
Regards,
~ Simon
the sender by reply email and
destroy all copies of the original message.
-Original Message-
From: Adam Winer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 22, 2007 10:57 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
If you remove the doctype-root-element
the sender by reply email and
destroy all copies of the original message.
-Original Message-
From: Perkins, Nate-P63196 [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 9:56 AM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2
Adam,
I've noticed that the combination
message.
-Original Message-
From: Perkins, Nate-P63196 [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 9:56 AM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2
Adam,
I've noticed that the combination of the trh:head tag (which outputs a
doctype) and my
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 22, 2007 10:57 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
If you remove the doctype-root-element, doctype-system,
and doctype-public off of jsp:output, does the problem
go away? It looks as though that doctype is getting
22, 2007 10:57 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
If you remove the doctype-root-element, doctype-system,
and doctype-public off of jsp:output, does the problem
go away? It looks as though that doctype is getting
pushed straight
AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
Hello Nate,
So what you're saying is that your application will only ever work in
quirk
mode? There's always a solution in standard mode as well, sometimes a bit
more complicated though
Hi,
I'm testing my project with 1.0.2 and I am having several issues.
1. No PPR activity works, I get a javascript error Invalid PPR
response any time I try to submit a PPR action
Can anyone give me a clue as to what's wrong and how to fix it?
2. My skin no longer works, it seems that a few of
Discussion
Subject: [Trinidad] Upgrading to 1.0.2
Hi,
I'm testing my project with 1.0.2 and I am having several issues.
1. No PPR activity works, I get a javascript error Invalid PPR
response any time I try to submit a PPR action
Can anyone give me a clue as to what's wrong and how to fix
On 8/22/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote:
Hi,
I'm testing my project with 1.0.2 and I am having several issues.
1. No PPR activity works, I get a javascript error Invalid PPR response
any time I try to submit a PPR action
PPR's been overhauled. But also tested quite a lot.
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2
A simple usecase is to call launchDialog
Nate Perkins
480-441-3667
[EMAIL PROTECTED]
I will try to make a minimal example as, admittably, my pages are
somewhat complex, but it is not limited to a certain action or a certain
behaviour
: [Trinidad] Upgrading to 1.0.2
Hi,
I'm testing my project with 1.0.2 and I am having several issues.
1. No PPR activity works, I get a javascript error Invalid PPR response any
time I try to submit a PPR action
Can anyone give me a clue as to what's wrong and how to fix it?
2. My skin
: Wednesday, August 22, 2007 4:28 PM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2
Regarding the problem with PPR, I had a similar problem with that
soon after the PPR stuff was changed for 1.0.2 (see topic in the dev
list named [Trinidad] AJAX PPR - Invalid PPR Response error
]
Sent: Wednesday, August 22, 2007 4:28 PM
To: MyFaces Discussion
Subject: RE: [Trinidad] Upgrading to 1.0.2
Regarding the problem with PPR, I had a similar problem with that
soon after the PPR stuff was changed for 1.0.2 (see topic in the dev
list named [Trinidad] AJAX PPR - Invalid PPR
, August 22, 2007 1:35 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
On 8/22/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote:
Hi,
I'm testing my project with 1.0.2 and I am having several issues.
1. No PPR activity works, I get a javascript error Invalid PPR
response
any
Adam Winer wrote:
2. My skin no longer works, it seems that a few of the selectors have
changed, namely:
a) the panelHeader is rendering with af_messages_header class
b) the panelBox has lost its background, it seems like there is no
longer a distinction between panelBox
Ok - I think I found my answer in SVN. I basically replaced the version of
MessageBoxRenderer in 1.0.2 (559575) with the one in HEAD (565851). After
replacing and doing a maven install (all tests passed), the issue is fixed
in my app. Here is a link to the diff:
email and
destroy all copies of the original message.
-Original Message-
From: Adam Winer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 22, 2007 1:35 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Upgrading to 1.0.2
On 8/22/07, Perkins, Nate-P63196 [EMAIL PROTECTED] wrote
33 matches
Mail list logo
