|
|
Rank: Advanced Member
Groups: Member
Joined: 6/3/2016
Posts: 32
|
I noticed that the handler (NewWindowHandler) for NewWindow event of EO.Wpf.WebView is still using the reference from EO.WebBrowser - and the NewWindowEventArgs WebView property still reference the old namespace. I know that the 'new' Wpf.WebView is just an 'alias' of the oldone and they can all be casted as we wish, but I still think the code should be consistent.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
This is by design. The basic rule is all core classes are platform neutral and they are all in EO.WebBrowser or EO.WebEngine namespace. WPF related classes are in EO.Wpf namespace. So there is no "old" or "new" namespace here. These are two different groups of classes.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/3/2016
Posts: 32
|
Noted. Thanks.
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/3/2016
Posts: 32
|
However, the confusion remain. I tried to open a new tab via javascript (submit form with a target=_blank). This one worked. Now, the new tab stays blank. Also, the 'caller' tab gets a BeforeNavigate event and gets white too.
Did something changed in this area?
Is there any wpf-browser sample I can play with - as it used to be before? I would like to compare the code to see what exactly have been changed and to adapt my code - if case.
Right now, I wish I stayed with the old version, the one I had in December ...
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
We are not aware of any change on this area. You can take a look of our TabbedBrowser sample application. That is a WPF based application.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/3/2016
Posts: 32
|
It looks like the fix from the new-tab-options solved this issue as well. Thank you.
|
|