loadcomponent | flexible JS and CSS static resource file loader | REST library

Where does the ScrollViewer come from?

During the testing, it only occurs there is on other control could be focused, and the ScrollViewer should be the visual container that use to render control, And you could find the Button with visual tree helper from the ScrollViewer. And you could use the following code to find the root parent of Button is ScrollViewer.

In CakePHP 3.9.3 support for samesite with CSRF cookies has been added, you'd have to switch to the CSRF protection middleware though.

If you can't upgrade, then you'll a bit of custom code, namely a custom/extended CSRF component that accepts further options for the attribute, and a custom/exteneded response object that creates cookies with that attribute accordingly.

In PHP versions earlier than PHP 7.3, you can, respectively must inject the SameSite attribute by utilizing the cookie path hack, which consists of appending further cookie attributes to the path, by simply closing the path of with a semicolon. In PHP versions as of PHP 7.3 you would use the as of then supported samesite for setcookie().

btw, for session cookies you'd modify your session.cookie_path or session.cookie_samesite PHP INI options accordingly, and other places in CakePHP that set cookies would possibly need to be adapted too, for example the cookie component, even if your app doesn't use it, it might be used by 3rd party plugins.

Example:

You are mixing up the old auth component and the new authentication plugin, the Auth.afterIdentify event belongs to the former.

The authentication plugin's authentication component has a Authentication.afterIdentify event, but this only applies to authenticators that are stateful and do not implement automatic persisting. So out of the box this only applies to the Form authenticator, and the event is being triggered once on the request where the user was authenticated via the form, on subsequent requests where they are authenticated via for example the Session authenticator, the event is not being triggered.

This is how I resolved the issue..

As the developer tool was not displaying any details of the error. I opened the node_modules@angular\router\bundles\router.umd.js and search for the error "Unhandled Navigation Error". On exception it was throwing this error without any detail, I added a link of code to write the whole exception in the console. After I ran the application, I saw the details of the err:

After debugging the router code, I found out that "window.history.replaceState()" and "window.history.pushState()" are null. May be word addin is making those null. That I couldn't figure out. As my code is pretty simple and doesn't refer any third party Javascript API ( not even office.js).

I added the following code in the index.html and that resolved the issue:

Apparently when this Component class passes thru the ngrx action's serialization it gets frozen and we cannot use it to construct new instances.

We can use the following workaround to make it working, until we find a better way. In app.module.ts, to your StoreModule's initializer add:

You can create an IMultiValueConverter in order to bind bind the object state and the current control. Then you can leverage the FindResource method defined on FrameworkElement to get a resource.

Derive from official document about optional package, when you deploy main app project, you need to ensure that both packages are in sync. Please refer to the following steps to solve it. In the main app project, navigate to the project build properties and select Compile with .NET Native tool chain. Go go to the project debug properties and select Deploy optional packages.

In addition, Application.LoadComponent Method is suitable for loading xaml files, not for loading pictures. So you could delete the code about loading image.

Update:

I suggest you could write image control in the HalloPage.xaml, which makes the image can be loaded along with the page. As follows:

HalloPage.xaml

The issue might be caused by a spelling mistake of the resource name that you defined in the Page.Resources or App.Resources.Please check where you are setting the resources and make sure the spelling is correct.

from this answer: removed both "aws/aws-sdk-php": "3.0", and "league/flysystem-aws-s3-v3": "~1.0", "league/flysystem-cached-adapter": "1.0", from composer.json

and run composer require league/flysystem-aws-s3-v3