Renamed to ken-matsui/html-styled-extra. It is published under that name, and new versions come out there.
Versions published as matken11235/html-styled-extra still install under that name. 2 versions of 3 come from the new location (see their notes). 1 version could not be recovered and cannot be installed.
Rerouted (cache, verified). The original is gone. This copy comes from a Lamdera package cache made before it went. The Lamdera package server serves a copy recovered from a Lamdera package cache from 2021-02-13.
What we checked: Rebuilt from the unpacked sources in a Lamdera package cache (5 copies agree), which Elm only writes after the published SHA-1 checked out; elm.json is byte-identical to package.elm-lang.org's; the exposed modules match docs.json; the zip is our own, so its SHA-1 is not the published one.
The Lamdera compiler uses this copy and prints a one-line notice saying so. elm itself fails to download this version.
Details · package.elm-lang.org's zip: https://github.com/matken11235/html-styled-extra/zipball/1.0.1/
This module contains types and values you can use to build up a list of
autocomplete tokens for form fields. Simple values like `On` or `Off` are
available, as well as more complex, nestable values: `Detailed <| Section "red"
<| Shipping <| Contact (Just Fax) Telephone`.
You'll probably want to import this module with an alias:
import Html.Styled exposing (input)
import Html.Styled.Attributes.Autocomplete as Autocomplete
import Html.Styled.Attributes.Extra exposing (autocomplete)
myShippingEmailInput =
input
[ autocomplete <|
Autocomplete.Detailed <|
Autocomplete.Shipping <|
Autocomplete.Contact Nothing <|
Autocomplete.Email
]
[]
Check out the [HTML Spec][spec] for more information about the `autocomplete`
attribute and the autocomplete detail tokens, such as their meaning, valid
controls, and inputformat.
[spec]: https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill
Build the attribute value for a Completion.
The base type for detailed autocomplete attributes. Some of these are
simple, like Email, while some allow nesting of autocomplete tokens, like
Billing Email.
Build a list of autocomplete tokens for a DetailedCompletion.
The optional contact types a ContactCompletion can be tagged with.
Transform a ContactType into it's autocomplete detail token.
Autocomplete tokens with the ability to be tagged with a ContactType.
Transform a ContactCompletion into it's autocomplete detail token.
This is the generalized completion value. You explicitly toggle completion on or off, or use a more complex
DetailedCompletion.