Project

General

Profile

Bug #1600

Wt internal error when widgets(WPushButton) has been replaced on page refresh (initiated form browser)

Added by Стойчо Стефанов Stoycho Stefanov almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
12/11/2012
Due date:
% Done:

0%

Estimated time:

Description

Hallo,

when a browser reloads the page and a widget have own specialization of WWebWidget::refresh(), where child widgets are replaced, using the new widgets (WPushButton) end up with "Wt internal error". The error message is different depending on the browser.

Firefox:

Wt internal error: TypeError: a is null, code: undefined, description: undefined

When the WWebWidget::refresh() method of the parent widget is called by an explicit button click, let us call that a "local reload", the page reloads properly, i.e., refresh() is propagated to the child widgets and the new widgets work fine. Moreover, when the error occurs the application's functionalities could be recovered using that "local reload".

Wt version: Wt-3.2.3

I narrowed the problem down to a test case (source file attached).

Regards,

Stoycho


Files

test.cpp (2.2 KB) test.cpp test case Стойчо Стефанов Stoycho Stefanov, 12/11/2012 12:16 PM
wt_config.xml (21.9 KB) wt_config.xml Стойчо Стефанов Stoycho Stefanov, 01/02/2013 11:52 AM
test.cpp (2.45 KB) test.cpp same test + some additional prints Стойчо Стефанов Stoycho Stefanov, 02/05/2013 07:54 AM
#1

Updated by Koen Deforche almost 8 years ago

  • Status changed from New to InProgress
  • Assignee set to Koen Deforche
#2

Updated by Koen Deforche almost 8 years ago

  • Status changed from InProgress to Feedback

Hey,

With what version of Wt do you see problems? Trying with the latest git I couldn't see any problems.

Regards,

koen

#3

Updated by Стойчо Стефанов Stoycho Stefanov almost 8 years ago

Hey,

my actual wt version is 3.2.3. Unfortunately, I cannot test it whit the git version until January. I'll do it as soon as possible, but not before 3th of January 2013.

Regards,

Stoycho

#4

Updated by Стойчо Стефанов Stoycho Stefanov almost 8 years ago

Hey Koen,

I see this error with the latest git version as well (svn revision 810). You should try the following: press F5 and than click on the application's "start" button.

regards,

Stoycho

#5

Updated by Стойчо Стефанов Stoycho Stefanov almost 8 years ago

Hey Koen,

I forgot to give you the config file.

false

seems to be crucial.

Regards,

Stoycho

#6

Updated by Koen Deforche over 7 years ago

  • Status changed from Feedback to InProgress
  • Target version set to 3.3.0
#7

Updated by Koen Deforche over 7 years ago

  • Status changed from InProgress to Feedback

Hey,

Could you provide a complete test-case ? This one has several methods missing ?

Or perhaps trim down the test case to something smaller that still shows the defect ?

Regards,

koen

#8

Updated by Стойчо Стефанов Stoycho Stefanov over 7 years ago

Hey Koen,

sorry, but I cannot see what is missing in this test case. For me it works and can demonstrate the problem. I just added some prints.

The only thing you have to do is to start a new session and click on the button "start (2)" and you'll get the error message. Close the message and click on the application's "refresh" button. A new button is created ("start (3)") which works fine (some processing is done on click). You can further replace the "start" button using "refresh" and the new button will be ok. But if you use the browser's refresh or just press F5 and click the new "start" button you'll get the error massage again.

I found an work around for the special case in my application, but it seems to be a bug and I'll be happy to help to find and fix it.

regards,

Stoycho

#9

Updated by Koen Deforche over 7 years ago

Hey Stoycho,

Ooops, I'm sorry. I seem to have messed up test-cases and bug reports. Your test case indeed is completely fine and much appreciated.

I'll get on it right away. Sorry for the confusion !

Regards,

koen

#10

Updated by Koen Deforche over 7 years ago

  • Status changed from Feedback to InProgress
#11

Updated by Koen Deforche over 7 years ago

  • Status changed from InProgress to Resolved

Hey,

Fixed in my git copy.

Regards,

koen

#12

Updated by Koen Deforche over 7 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF