<mailto:dev@wicket.apache.org>
Gesendet: Donnerstag, 15. Februar 2018 16:48:18
Betreff: Re: [VOTE] Release Apache Wicket 8.0.0-M9
Hi,
I need your help. what's exactly the cavea
n worse, an app that may work well in local mode may break in
>>>> production as network timing as well as client CPU count (influences
>>>> thread) and speed of CPU and or GPU (yep... ) may change the timings the
>>>> event DOMContentLoaded gets fired;
>>>>
ources (defered or not) so that the page itself
cant break because of this
- Ursprüngliche Mail -
Von: "Andrea Del Bene"
An: dev@wicket.apache.org
Gesendet: Donnerstag, 15. Februar 2018 16:48:18
Betreff: Re: [VOTE] Release Apache Wicket 8.0.0-M9
Hi,
I need your help. what'
or wicket but had no time yet to
> > try it out; Idea is to create the wicket object in the head at first
> inline
> > script before any JS resources (defered or not) so that the page itself
> > cant break because of this
> >
> >
> > - Ursprüngliche Mail -
&
> >>> event DOMContentLoaded gets fired;
> >>>
> >>> even JQuery guys are plagued by this and have no real solution to it
> now
> >>> IMHO https://github.com/jquery/jquery/issues/3271
> >>>
> >>> I think we can get a re
/jquery/jquery/issues/3271
>>>
>>> I think we can get a real working one for wicket but had no time yet to
>>> try it out; Idea is to create the wicket object in the head at first
>> inline
>>> script before any JS resources (defered or not) so that the pa
line
> > script before any JS resources (defered or not) so that the page itself
> > cant break because of this
> >
> >
> > - Ursprüngliche Mail -
> > > Von: "Andrea Del Bene"
> > > An: dev@wicket.apache.org
> > > Gesendet: Donners
JS resources (defered or not) so that the page itself
> cant break because of this
>
>
> - Ursprüngliche Mail -
> > Von: "Andrea Del Bene"
> > An: dev@wicket.apache.org
> > Gesendet: Donnerstag, 15. Februar 2018 16:48:18
> > Betreff: Re: [VO
ct in the head at first inline script
before any JS resources (defered or not) so that the page itself cant break
because of this
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> An: dev@wicket.apache.org
> Gesendet: Donnerstag, 15. Februar 2018 16:48:18
> Betreff
Hello Andrea
The description is here
https://issues.apache.org/jira/browse/WICKET-6498?focusedCommentId=16349021&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16349021
Am not observing any "races" in our main app, so I can't describe it myself
:(
On Thu, Feb 15,
Hi,
I need your help. what's exactly the caveat about WICKET-6498? It uses
javascript events that might not be supported buy browser?
On Sun, Feb 11, 2018 at 6:16 PM, Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:
> +1 to release for M9
>
> IMHO a warning should be added with regards
Hi Andrea,
that's a good idea. WICKET-6189 is another contender for mentioning in the
release notes.
Sven
Gesendet mit Blue
Am 12. Feb. 2018, 12:50, um 12:50, Andrea Del Bene
schrieb:
>Sorry, when I said "change log" I actually meant the release note.
>
>On Mon, Feb 12, 2018 at 12:48 PM,
+1
Tested:
1) signatures
2) my main app
On Mon, Feb 12, 2018 at 3:17 PM, Maxim Solodovnik
wrote:
> +1
>
> Tested:
> 1) signatures
> 2) build from sources
> 3) our main app
>
>
> I would slightly modify build script
> Right now I'm getting
>
> sha256sum -c apache-wicket-8.0.0-M9.tar.gz.sha256
>
ev@wicket.apache.org
> > Gesendet: Sonntag, 11. Februar 2018 21:24:53
> > Betreff: Re: [VOTE] Release Apache Wicket 8.0.0-M9
>
> > Hi,
> >
> > JavaScriptDeferHeaderResponse is an *alternative* to
> > JavaScriptFilteredIntoFooterHeaderResponse, it doesn&#x
Sorry, when I said "change log" I actually meant the release note.
On Mon, Feb 12, 2018 at 12:48 PM, Andrea Del Bene
wrote:
> Hi,
>
> On Mon, Feb 12, 2018 at 12:38 PM, Sven Meier wrote:
>
>> Hi Andrea,
>>
>> read here:
>>
>> https://cwiki.apache.org/confluence/display/WICKET/Migration
>> +to+Wi
Hi,
On Mon, Feb 12, 2018 at 12:38 PM, Sven Meier wrote:
> Hi Andrea,
>
> read here:
>
> https://cwiki.apache.org/confluence/display/WICKET/Migration
> +to+Wicket+8.0#MigrationtoWicket8.0-Application'sIHeaderResp
> onseDecoratorASFJIRAkey,summary,type,created,updated,
> due,assignee,reporter,prio
Hi Andrea,
read here:
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+8.0#MigrationtoWicket8.0-Application'sIHeaderResponseDecoratorASFJIRAkey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution5aa69414-a9e9-3523-82ec-879b028fb15bWICKET-6498
...
Hi Sven,
what I noticed with my application and with one of the tutorial examples is
that with the current solutions based on
JavaScriptFilteredIntoFooterHeaderResponse
some header item are "swallowed" without being rendered. Missing items
usually are Wicket internal javascript files like wicket-e
thanks a lot Sven!
- Ursprüngliche Mail -
> Von: "Sven Meier"
> An: dev@wicket.apache.org
> Gesendet: Sonntag, 11. Februar 2018 21:24:53
> Betreff: Re: [VOTE] Release Apache Wicket 8.0.0-M9
> Hi,
>
> JavaScriptDeferHeader
+1
kind regards
Tobias
> Am 11.02.2018 um 21:24 schrieb Sven Meier :
>
> Hi,
>
> JavaScriptDeferHeaderResponse is an *alternative* to
> JavaScriptFilteredIntoFooterHeaderResponse, it doesn't break anything - but
> even if you wanted to, you could use both simultaneously.
>
> Regarding WICKE
Hi,
JavaScriptDeferHeaderResponse is an *alternative* to
JavaScriptFilteredIntoFooterHeaderResponse, it doesn't break anything -
but even if you wanted to, you could use both simultaneously.
Regarding WICKET-6498's experimental status - I've added the following
to the JavaDoc:
* Note: Thi
Good point. We should also underline that WICKET-6498 breaks custom
response decoration that might be used to place JavaScript inside body tag.
On 11/02/2018 18:16, Korbinian Bachl wrote:
+1 to release for M9
IMHO a warning should be added with regards to WICKET-6498 as it is not yet
working
+1 to release for M9
IMHO a warning should be added with regards to WICKET-6498 as it is not yet
working in a reliable way but may break depending on client specifics;
- Ursprüngliche Mail -
> Von: "Andrea Del Bene"
> An: dev@wicket.apache.org
> Gesendet: Sonntag, 11. Februar 2018 17:34
23 matches
Mail list logo
