background:
Quite easily I've got the Fuelux Wizard working.
I now wanted to introduce a date picker in one of the steps.
I did get the datepicker working fine outside of the wizard.
my problem:
when I introduced it into the form i have had problems.
The next and previous buttons do work but the page is immediately reloaded.
I debugged through the code and I see that the calendar is updated but then
the jquery event handling code returns and then my page is reloaded.
I'm at a loss to understand why the page is being reloaded.
I'm guessing that it is something to do with the event handling in the wizard
- as this html code works perfeclty outside of the wizard.
Any ideas ?
Has anybody got this working ?
Related
I am working on a usual crud application in React. You can add a party to the list and each party list item can be edit, deleted etc. Currently, I am working on the grey + button which should increment the votes by 1 each time the button gets clicked.
UI of the application
However, as soon as I click the button, the application breaks with the following error code.
Error Code
I am trying to update a component using setState(), but its not working. I thought somebody might help. I have been trying for 3 days, but nothing works. I have to admit that I am a beginner.
Here is a link to the current code .
https://github.com/Benni8753/Election2021.git
Thanks in advance.
Benjamin
In my App, While navigating from one form to another, I found an issue with both android and IOS debug build. This will happen only when second form contains any type of Picker control. I have added logic to navigating to second form on click of a button on the first form. So now when I click the button, Picker control of the second form open up on first form instead of navigating to second form. Second form will appear only after I made the selection on Picker Control. This issue is happening on bother android and IOS builds. Please advise if any one encounter similar issue with recent debug builds.
This happens only when Picker is first control on the form.
Code used for Picker:
Picker firstAppForm = new Picker();
String[] options = {"Tabbed Menu", "My Schedule "};
firstAppForm.setStrings(options);
firstAppForm.setUIID("TextField");
firstAppForm.setAutoSizeMode(true);
I tried to reproduce it and wasn't able to but I did run into a null pointer exception related to the native picker which might be the underlying cause of this.
I've pushed out a fix that should be available now so if you send a new build this will hopefully be resolved.
as a reference, I've published three videos to help illustrate the current problems I'm facing and probably #Chris L as well, maybe this aid in finding out the root of the problem. The links can be found as a comment to the initial publication.
We are using angular-material's md-tabs to display information to the user.
Up until now we used an on-demand approach by adding
ng-click=vm.getForExampleDataForTab1(),
ng-click=vm.getForExampleDataForTab2()
and so on for each md-tab. But this solution has a problem that the first tab is displayed with no data because it doesn't get clicked by the user. So we switched to md-on-select instead. And that did the trick, the first tab was getting data and all was fine. Apparently. We then discovered in Chrome's Dev tools that when moving to another page in the app, all the other tabs that were not selected (the user didn't click on them to view the data) were called.
Did anyone encounter such a behaviour? It only happens when we used md-on-select, not ng-click on the tabs.
Thanks a lot,
ashilon
I came accross a form wizard by Afrad on github material-wizard and will like to implement it because of its angular-material properties. The downside is that the text-boxes turn out totally different from the angular styling. Is there a way to fix this? what causes this and how do you go about the fix. I have tried using ngWizard as well and face the same issue. the forms display okay without being encapsulated in the wizard directive.
A link to a plunker showing the demo is on the github page. Attached below is a snapshot of the plunker.
I created a long form using Angular Material. Weird thing is that instead of the page displaying normally it starts off midway through the form.
Is this something my browser is doing (Perhaps it thinks I left off at a certain point last time)?
Not sure how to force the page to load normally and start from the top.
Has anyone encountered this before?
I was able to track down the issue and it was the md-autocomplete field causing the page to scroll down. To fix this I added md-autofocus="false" in the md-autocomplete field and now it loads normally.