Re: Generic message when component feedback has error

[Sebastien]

Hi,

Some leads:
- session#error
- component.send(BREATH, component.getPage(), MyErrorPayload(myMessage))

(typing from mobile, arguments might not be in the correct order)

Hope this helps
Sébastien





On Apr 19, 2017 21:47, "Entropy"  wrote:

We're using component feedback panels, and when a component has a message we
are filtering that message out from the parent with a filter that tosses
anything that doesn't link to the form or page.  Works fine.

However, when there is a component message on any component, we want a
generic message like "You have errors" or whatever in the top feedback.
Only once.  And associated with the poage or form.

So I clearly don't want to add it via the validators, I'd get a bunch.  Is
there a right place to add that?

--
View this message in context: http://apache-wicket.1842946.
n4.nabble.com/Generic-message-when-component-feedback-has-
error-tp4677729.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Generic message when component feedback has error

[Entropy]

We're using component feedback panels, and when a component has a message we
are filtering that message out from the parent with a filter that tosses
anything that doesn't link to the form or page.  Works fine.

However, when there is a component message on any component, we want a
generic message like "You have errors" or whatever in the top feedback. 
Only once.  And associated with the poage or form.

So I clearly don't want to add it via the validators, I'd get a bunch.  Is
there a right place to add that?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Generic-message-when-component-feedback-has-error-tp4677729.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Weird CSS warning in IE

[Maxim Solodovnik]

I'm not able to reproduce it anymore :(
will monitor the logs

On Mon, Apr 10, 2017 at 9:50 PM, Maxim Solodovnik 
wrote:

> Hello Sebastien,
>
> I was able to see it in our application, I'll try to create small
> application with this issue
>
> On Mon, Apr 10, 2017 at 9:16 PM, Sebastien  wrote:
>
>> Hi Maxim,
>>
>> I activated the developer tools in IE but I can't see this behavior from
>> the demo site. Is there anything else to do or a special page to go?
>>
>> Thanks,
>> Sebastien.
>>
>>
>>
>> On Sat, Apr 8, 2017 at 12:06 PM, Maxim Solodovnik 
>> wrote:
>>
>>> Thanks a lot!
>>>
>>> On Sat, Apr 8, 2017 at 5:04 PM, Sebastien  wrote:
>>>
 Hi Maxim,

 I will check on monday with IE...

 Thanks & best regards,
 Sebastien.


>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Re: "/websocket/closed" is not working in IE11

[Maxim Solodovnik]

The issue is not reproducible using simple quick-start :(
The only option seems to be to subscribe to error event as well :(

sorry for the noise

On Mon, Apr 10, 2017 at 3:09 PM, Maxim Solodovnik 
wrote:

> Weird enough, quickstart works :(
> Investigation only begins :)
>
> On Mon, Apr 10, 2017 at 2:04 AM, Martin Grigorov 
> wrote:
>
>> On Sat, Apr 8, 2017 at 11:41 AM, Maxim Solodovnik 
>> wrote:
>>
>> > Hello All,
>> >
>> > I just have noticed "/websocket/closed" is not working in IE11
>> > handler set via
>> > Wicket.Event.subscribe("/websocket/closed", function() {})
>> > Is not fired
>> >
>> > The following message displayed in console instead:
>> > SCRIPT12030: WebSocket Error: Network Error 12030, The connection with
>> the
>> > server was terminated abnormally
>> >
>> > Wicket: 8.0.0-M5
>> > OS: Win7/Win10
>> > Browser: IE11/Edge
>> >
>> > Should I file JIRA?
>> >
>>
>> Yes, with a quickstart please!
>>
>>
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>> >
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax