guest271314 (2019-05-23T23:44:20.000Z)
guest271314 at gmail.com (2019-05-23T23:59:53.173Z)
> I want to avoid dealing with HTML Using HTML is part of premise of the proposal, correct? Am still not sure what the actual requirement is. If the requirement is to prevent duplicate _values_ being input by the user you can utilize ```pattern``` attribute of ```<input>``` with a ```RegExp``` which matches the current values of ```<input>``` elements, ```oninvalid``` and ```checkValidity()``` which will provide the functionality of the ```value``` attribute of ```<input>``` and ```<select>``` elements being unique as to a ```<form>``` element. If there is no user input there should not be any issue creating unique key-value pairs using ```Map```; ```WeakMap```; ```Set```, or other means. > and even more HTTP verb related things like `Form` and `FormData` and just deal with general JS objects, so I use Models instead of things like`FormData`. Am not certain what a "Model" is. A ```FormData``` object can be serialized and represented in various manners; including as an array of JavaScript arrays of key-value pairs that can be adjusted to the exact keys and values required ```[...formData]```; multipart/form-data; etc. An earlier post mentioned forms at > I can read and write "Form Fields" quickly Is user input involved in the procedure relevant to "Indexing HTML Attributes and Unique Indexes"? What are you trying to achieve that you are _not_ able to with the current code? What do you consider to be "general JS objects"?
guest271314 at gmail.com (2019-05-23T23:58:44.752Z)
> I want to avoid dealing with HTML Using HTML is part of premise of the proposal, correct? Am still not sure what the actual requirement is. If the requirement is to prevent duplicate _values_ being input by the user you can utilize ```pattern``` attribute of ```<input>``` with a ```RegExp``` which matches the current values of ```<input>``` elements, ```oninvalid``` and ```checkValidity()``` which will provide the functionality of the ```value``` attribute of ```<input>``` and ```<select>``` elements being unique as to a ```<form>``` element. If there is no user input there should not be any issue creating unique key-value pairs using ```Map```; ```WeakMap```; ```Set```, or other means. > and even more HTTP verb related things like `Form` and `FormData` and just deal with general JS objects, so I use Models instead of things like `FormData`. A ```FormData``` object can be serialized and represented in various manners; including as an array of JavaScript arrays of key-value pairs that can be adjusted to the exact keys and values required ```[...formData]```; multipart/form-data; etc. An earlier post mentioned forms at > I can read and write "Form Fields" quickly Is user input involved in the procedure relevant to "Indexing HTML Attributes and Unique Indexes"? What are you trying to achieve that you are _not_ able to with the current code? Am not certain what a "Model" is. What do you consider to be "general JS objects"?
guest271314 at gmail.com (2019-05-23T23:56:42.711Z)
> I want to avoid dealing with HTML Using HTML is part of premise of the proposal, correct? Am still not sure what the actual requirement is. If the requirement is to prevent duplicate _values_ being input by the user you can utilize ```pattern``` attribute of ```<input>``` with a ```RegExp``` which matches the current values of ```<input>``` elements, ```oninvalid``` and ```checkValidity()``` which will provide the functionality of the ```value``` attribute of ```<input>``` and ```<select>``` elements being unique as to a ```<form>``` element. If there is no user input there should not be any issue creating unique key-value pairs using ```Map```, ```WeakMap``` or ```Set```. > and even more HTTP verb related things like `Form` and `FormData` and just deal with general JS objects, so I use Models instead of things like `FormData`. A ```FormData``` object can be serialized and represented in various manners; including as an array of JavaScript arrays of key-value pairs that can be adjusted to the exact keys and values required ```[...formData]```; multipart/form-data; etc. An earlier post mentioned forms at > I can read and write "Form Fields" quickly Is user input involved in the procedure relevant to "Indexing HTML Attributes and Unique Indexes"? What are you trying to achieve that you are _not_ able to with the current code? Am not certain what a "Model" is. What do you consider to be "general JS objects"?
guest271314 at gmail.com (2019-05-23T23:54:37.592Z)
> I want to avoid dealing with HTML Using HTML is part of premise of the proposal, correct? Am still not sure what the actual requirement is. If the requirement is to prevent duplicate _values_ being input by the user you can utilize ```pattern``` attribute of ```<input>``` with a ```RegExp``` which matches the current values of ```<input>``` elements, ```oninvalid``` and ```checkValidity()``` which will provide the functionality of the ```value``` attribute of ```<input>``` and ```<select>``` elements being unique as to a ```<form>``` element. If there is no user input there should not be any issue creating unique key-value pairs using ```Map```, ```WeakMap``` or ```Set```. > and even more HTTP verb related things like `Form` and `FormData` and just deal with general JS objects, so I use Models instead of things like `FormData`. A ```FormData``` object can be serialized and represented in various manners; including as an array of JavaScript arrays of key-value pairs that can be adjusted to the exact keys and values required ```[...formData]```; multipart/form-data; etc. An earlier post mentioned forms at > I can read and write "Form Fields" quickly Is user input involved in the procedure relevant to "Indexing HTML Attributes and Unique Indexes"? Am not certain what a "Model" is. What do you consider to be "general JS objects"?
guest271314 at gmail.com (2019-05-23T23:53:43.411Z)
> I want to avoid dealing with HTML Using HTML is part of premise of the proposal, correct? Am still not sure what the actual requirement is. If the requirement is to prevent duplicate _values_ being input by the user you can utilize ```pattern``` attribute of ```<input>``` with a ```RegExp``` which matches the current values of ```<input>``` elements, ```oninvalid``` and ```checkValidity()``` which will provide the functionality of the ```value``` attribute of ```<input>``` and ```<select>``` elements being unique as to a ```<form>``` element. If there is no user input there should not be any issue creating unique key-value pairs using ```Map```, ```WeakMap``` or ```Set```. > and even more HTTP verb related things like `Form` and `FormData` and just deal with general JS objects, so I use Models instead of things like `FormData`. A ```FormData``` object can be serialized and represented in various manners; including as an array of JavaScript arrays of key-value pairs that can be adjusted to the exact keys and values required ```[...formData]```; multipart/form-data; etc. An earlier post mentioned forms at > I can read and write "Form Fields" quickly Is user input involved in the procedure relevant to "Indexing HTML Attributes and Unique Indexes"? Am not certain what a "Model" is. What do you consider to be "general JS objects"?
guest271314 at gmail.com (2019-05-23T23:50:49.746Z)
> I want to avoid dealing with HTML Using HTML is part of premise of the proposal, correct? Am still not sure what the actual requirement is. If the requirement is to prevent duplicate _values_ being input by the user you can utilize ```pattern``` attribute of ```<input>``` with a ```RegExp``` which matches the current values of ```<input>``` elements, ```oninvalid``` and ```checkValidity()``` which will provide the functionality of the ```value``` attribute of ```<input>``` and ```<select>``` elements being unique as to a ```<form>``` element. If there is no user input there should not be any issue creating unique key-value pairs using ```Map```, ```WeakMap``` or ```Set```. > and even more HTTP verb related things like `Form` and `FormData` and just deal with general JS objects, so I use Models instead of things like `FormData`. A ```FormData``` object can be serialized and represented in various manners; including as an array of JavaScript arrays of key-value pairs that can be adjusted to the exact keys and values required ```[...formData]```; multipart/form-data; etc. An earlier post mentioned forms. Am not certain what a "Model" is. What do you consider to be "general JS objects"?