Re: Debugging Problems and strange behavior
Posted: Tue Nov 19, 2019 1:23 pm
Good news, it shows google now! Finally! :D
Thank you for that special Demo. The actual problem (the white window) was here:
(debug_log)
[1119/135829.008:VERBOSE1:script_context.cc(117)] Created context:
extension id: (none)
frame: 395A1A38
URL:
context_type: WEB_PAGE
effective extension id: (none)
effective context type: WEB_PAGE
The URL was empty, and that was because I forgot to set the Default_URL... I don't know why the BrowserCreatedMsg procedure is still not executed but with the default URL it finally shows something.
But there is still a last problem left. The behavior, that the child form wont close. And the fact, that I now have to transform the toolbox into the embedded form (into the PWA Form, who is calling the child at the moment). But I think that seems to be possible.
Thank you for that special Demo. The actual problem (the white window) was here:
(debug_log)
[1119/135829.008:VERBOSE1:script_context.cc(117)] Created context:
extension id: (none)
frame: 395A1A38
URL:
context_type: WEB_PAGE
effective extension id: (none)
effective context type: WEB_PAGE
The URL was empty, and that was because I forgot to set the Default_URL... I don't know why the BrowserCreatedMsg procedure is still not executed but with the default URL it finally shows something.
But there is still a last problem left. The behavior, that the child form wont close. And the fact, that I now have to transform the toolbox into the embedded form (into the PWA Form, who is calling the child at the moment). But I think that seems to be possible.