Last 12 weeks ยท 0 commits
3 of 6 standards met
As I said in this issue, I've rearranged the attributes that may appear on the element, as well as new test cases for the element. In the following, I have bolded some of the content to be discussed. Please review it when you are free. @DaniGuardiola is also welcome to review it together. Any suggestions are very welcome. Attributes (spec) : Metadata name : Pragma directive : Value of the element : Character encoding declaration : Applicable media : Microdata, may appear on any HTML element Additional attributes (spec) : Extended attribute by RDFa, commonly used in the Open Graph protocol Rules Exactly one of the , , , and attributes must be specified. If either , , or is specified, then the attribute must also be specified. Otherwise, it must be omitted. If the attribute is present, its value must be an ASCII case-insensitive match for the string . There must not be more than one element with a attribute per document. The attribute says which media the metadata applies to. Additional rules If is specified, then the attribute must also be specified. (not for sure, but it seems to be true) If is not specified but is specified, then the attribute should be treated as attribute. (Do users need to be warned about this compatibility process?) If and are specified, then the attribute should be the same as attribute. (Does this rule should be added to simplify processing?) Test cases renders only valid meta renders only first meta with charset renders only last meta with the same name/property/http-equiv/itemprop renders only last meta with same media renders all meta with different media renders only last meta with same property WIP: meta with name&property mixed**
Repository: solidjs/solid-meta. Description: Write meta tags to the document head Stars: 154, Forks: 18. Primary language: TypeScript. Languages: TypeScript (96.2%), JavaScript (3.8%). Open PRs: 4, open issues: 25. Last activity: 22h ago. Community health: 62%. Top contributors: ryansolid, nksaraf, davedbase, github-actions[bot], ArnabXD, birkskyum, GoodbyeNJN, JakkuSakura, dennev, indeyets and others.
Reproduced example: https://stackblitz.com/edit/solidjs-templates-zamsr7?file=src/App.tsx Code Expected behavior Both meta tags render in the `` as would happen if you do: Observed behavior Only the latter of the 2 meta tags is rendered and the other just disappears.
I have essentially 2 pages, on and on. Now, basically the structure is like this: but the result is like this https://user-images.githubusercontent.com/4517582/217297678-42e7adf4-1a5d-4af3-8aa3-83423c07f52d.mov Why does the detail page that is currently not rendered still overwrite the `navigate('/', { resolve: false })`, not when I use the browser back/forward buttons.
[x] Addresses an existing open issue: [[Bug?]: SSR adds commas between children (in meta title)](https://github.com/solidjs/solid-start/issues/1931) In the situation of this issue, nested array inputs like do not flatten properly, so change to using a function that supports flattening nested structures.