I have added 'Home' title to the navigation item for the sake of accessibility, but it's still treated as a UIPageView
UI Test Activity:
Assertion Failure: XCTAssertEqual failed: ("Optional("UIPageView")") is not equal to ("Optional("Home")") -
It was not an accessibility issue with Xcode, I just selected the wrong controller (I'm using a UIPageViewController for navigation purposes), sorry for wasting your time ;P.
Related
After upgrading from Wicket 1.5 to Wicket 9, our users now may sometimes cause a Stale Page Exception by:
Duplicating a tab
Clicking a link, submitting a form, etc., in the second tab
Returning to the first tab
Trying to click a link, submit a form, etc., in the first tab
In the past, i.e. 1.5, Wicket's default behaviour on encountering a stale page exception was to recreate the original page. This gave the users a smooth and trouble-free experience, requiring just one extra click on the link or button in order to achieve their aim. They grew used to duplicating tabs, and wish to continue doing so.
Now, in Wicket 9, a stale page exception triggers a 500 error, which is seriously undesirable behaviour.
How can we return to the default behaviour that we had before? There must be a relevant setting somewhere, but I don't know where.
I would be most grateful if anyone can tell me how to change this setting. Thanks!
This problem is solved by upgrading to Wicket 9.3.0 or later.
I've been struggling with the implementation of Modal Navigation inside Tab Navigation in Nativescript. So I wondered if someone had a good practice on how to implement what I am looking for.
I've tried multiple ways but none worked, I might lack some deep knowledge about router navigation since most error concerned navigation.
Here is a playground that tries to replicate what I am trying to achieve: https://play.nativescript.org/?template=play-ng&id=VdmiR9&v=8
Errors that often occurred were:
CONSOLE ERROR [native code]: ERROR Error: No componentRef found in DetachedRouteHandle
ERROR Error: Uncaught (in promise): Error: StaticInjectorError(AppModule)[FirstModalComponent -> ModalDialogParams]
(While the ModalDialogService was injected inside the AppModule)
No component factory found for RootModalComponent. Did you add it to #NgModule.entryComponents
(While the RootModalComponent was added to the entryComponents of the lazy loaded module, so I added it to the AppModule)
Can't resolve '~/app' in...
(This error is weird because in some projects, the lazy loading of modules works with this import '~/app' while in other projects it fails)
Error: Cannot match any routes. URL Segment: 'tabs/default'
(This error occurred all the time, it seems I did not totally grasp the way of implementing routes)
If someone knows a way to do modal navigation inside tab navigation, it would help me a lot.
Currently, modal navigation inside a tabview is somewhat buggy in the Nativescript Angular framework, but there is a workaround. You can find a full implementation of this modal navigation inside this playground sample: https://play.nativescript.org/?template=play-ng&id=TkK7sQ&v=5
Fir further info, take a look at this issue I created on their GitHub repo: https://github.com/NativeScript/nativescript-angular/issues/1774
I am facing a weird problem in windows phone 8.1 page navigation.
I have got two pages.
Login page > Consists of app bar in which one of the button take us to second page.
Second page is Cached using MVVM i.e Registered the Second page to IOC on launch of app and binding the instance of it to page 2 XAML.
In the Second page View model Constructor I am making Server call to get the data.
Problems facing.
On Clicking the app bar button to navigate to second page, the app stays in the first page until the second page make server call and get the response. Then its navigating.
But actual behavior must be it should navigate to second page and wait there to get response showing progress bar.
One quick fix is I made the thread to stop for some 50 millisecond in page 2 constructor of view model and then made service call
It navigated to Second page immediately and waited there until response but the previous page App Bar still displays until I get the response.
I even find the quick solution for it by Collapsing the App bar just before Navigating to that page.
I know these quick fixes are not good. So please help me to find out the problem or if you already know please revert back with the solution.
Don't use constructor to initiate the web service calls . Use OnNavigatedTo or Page_Loaded event .
I am getting 'ViewExpiredException' on click of back button, in Chrome browser ONLY (IE and Firefox - no issue). This happens ONLY when the previous view has some ajax updates.
Load home.xhtml (let's say, javax.faces.viewState-sequence - 1)
Do some Ajax updates on home.xhtml (let's say, javax.faces.viewState-sequence - 2)
PRG and go to home.xhtml again (let's say, javax.faces.viewState-sequence - 3)
Press Chrome Back button.
Page loads. (Now view is having javax.faces.viewState-sequence - 2 - ISSUE is instead of having new sequence id - 4 it is getting the previous sequence id - 2. That means page may be loading from Cache. As I do remove the previous views from server, view with sequence id - 2 is not present).
Any click (post back/ajax) shows ViewExpiredException.
NOTE: If Step 2 above is skipped, there is no issue, as in the following
Load home.xhtml (let's say, javax.faces.viewState-sequence - 1)
PRG and go to home.xhtml again (let's say, javax.faces.viewState-sequence - 3)
Press Chrome Back button
Page loads. (It is having javax.faces.viewState-sequence - 4 - NO ISSUE. That means page IS NOT loading from Cache)
Any click (post back/ajax) - no issue.
Please note that I am on MyFaces 2.1.8 and I am also using NoCacheFilter as suggested by BalusC. That is why IE and Firefox has no issues, but issue is only with Chrome, and that too ONLY when the previous view has ajax updates.
Any help or pointers to fix the problem or your first thoughts, are very much appreciated.
Please let me know if any information that I might have missed and you may want to know.
Update: 6/27/14
In the above case, please advice if I could manually create and build the view when the restored view returns null during postback, using custom ViewHandler.
I have checked the answer to question, Can you POST to JSF2 page with an expired session?. But it is not working in my setup, and it shows the blank white page. Any idea. Is it because I am using MyFaces 2.1.8 and it has different implementation of state manager ?
Thanks very much in advance.
Best Regards,
Kumar.
I had the similar problem before.
I solved it in the following way:
Run Chrome and press F12 to execute Developer tools
Select Resources on the menu bar and then click Cookies
Select your website name and Clear all cookies.
It worked for me.
Just fixed this issue. With multiple forms in a page, each form will have a hidden input javax.faces.viewState. When loading page for a Back navigation, Chrome is loading these state input from cache, if the previous page had some ajax calls. My fix is to auto complete off on all forms, and hidden inputs are now loading fresh instead from cache. I hope this helps someone in need.
<script>
$(function(){
$('form').attr("autocomplete", "off");
});
</script>
Im creating an app (rather big one) with Worklight. When im testing the app in an android phone and press the backbutton it closes the app.. now i want it to go back one page. Right now the page navigation is with dojox mobile implemented system. this way:
<button data-dojo-type="dojox.mobile.ToolBarButton" data-dojo-props="transition:'fade',dir:'1',moveTo:'Contact'" class="buttonHem" style="color:black; font-size:1em;">Kontakta Oss</button>
is there a way to use the android backbutton without having to redo everything?
we have deadline in 2 weeks so there is really no time to redo the app with jquery mobile..
Answers will be appreciated.
If you're talking about a hardware Android back button you have a WL API to override it's behaviour.
WL.App.overrideBackButton(function() { doSomething });
and WL.App.resetBackButton();
The back button functionality should work in Dojo Mobile. Looking at the documentation for ToolBarButton I think what you need to do is use a # in front of your next view for the moveTo attribute. In your example it would be moveTo:'#Contact' Take a look at the moveTo attribute in the doc below for more info.
http://dojotoolkit.org/reference-guide/1.8/dojox/mobile/ToolBarButton.html