Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoJS, allow forms to work with JavaScript turned off #54

Closed
2 of 5 tasks
PatrickJS opened this issue Aug 6, 2015 · 11 comments
Closed
2 of 5 tasks

NoJS, allow forms to work with JavaScript turned off #54

PatrickJS opened this issue Aug 6, 2015 · 11 comments

Comments

@PatrickJS
Copy link
Member

The app needs to be able to work with JavaScript turned off. This is to allow older browsers (legacy) to function or large enterprise companies with crazy restrictions. Currently the links should be able to work with no problem. formDirectives(server)

this is done via action attribute in the <form> tag which makes a post request

  • Decorate for <form> tags with action and method attributes
  • Provide a way to pass data from the post request to the server
  • Provide a way to invoke the correct method via submit event on the server
  • Provide a way to only send down markup
  • Improve developer API
@tamascsaba
Copy link
Contributor

Nice feature 👍

@MarkPieszak
Copy link
Member

Good call Pat 👍

@wesleycho
Copy link
Contributor

For the submit event on the server, what would be necessary for that option? Would it be desired to plug in routing the action URI, or the user configuring the URI used for the action attribute?

Also what are the thoughts on how to determine if markup only is to be sent down? That seems like a problem perhaps separate from this in particular, and may be a larger issue than just involving forms.

@PatrickJS
Copy link
Member Author

This feature was placed on the shelf soon after I started it. A client needs this feature so I'll be working on this again in March (moving to P2 from P3). With the compiler refactors done since the initial version it may be easier to get it working

@PatrickJS PatrickJS self-assigned this Feb 15, 2016
@scarlz
Copy link

scarlz commented Jun 8, 2016

@gdi2290 We also require this feature for a large-scale project, and wondered how successful you were in implementing this for your client? I realise this feature is tagged with P2 and there is no milestone set, but in terms of viability, is there any expectation on when this might land?

@jamesbirrellgray
Copy link

@gdi2290 Is there a pull request or repo for this work you started? I work on a gov.uk project and we would like to contribute.

@thomasmeadows
Copy link

I thought this was supposed to be one of the reasons for server side rendering in a2. Many government entities need this and some companies are strict and allow very little or no XMLHTTP request.

@MarkPieszak
Copy link
Member

There is a large revamp / restructuring of Universal going on, but this is definitely a tough but important thing to have working (as you said for government etc agencies). We might have to wait for the restructuring before continuing on with this, but I'll try to help as well to get this going. @scarlz @jamesbirrellgray @thomasmeadows

@jamesbirrellgray
Copy link

@MarkPieszak thank you, let me know if we can help in anyway :-)

@PatrickJS
Copy link
Member Author

won't be supported officially
angular/angular#13822

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants