respec related conflicts with examples?

[w3c]

respec related conflicts with examples?

[r12a]

I believe it's because you set the example class on the pre element as well as the div element that contains it. It seems that this redundancy is generated by respec. I would certainly think that one example class should be sufficient.

[iherman]

The original, respec code is:

      <pre class="example highlight">
{
  "name": "inventory_date",
  "titles": "Inventory Date",
  "dc:description": "The date of the operation that was performed.",
  "datatype": {
    "base": "date",
    "format": "M/d/yyyy"
  }
}
      </pre>

Ie, it is definitely respec that adds both. But one would expect that changing the style sheet would not lead to such differences anyway...

[halindrome]

Hmm. We could change respec so that when it wraps the example in a div
it removes the class example from the pre... but that feels weird.

On Wed, Nov 11, 2015 at 2:33 AM, Ivan Herman [email protected]
wrote:

The original, respec code is:

  <pre class="example highlight">

{
"name": "inventory_date",
"titles": "Inventory Date",
"dc:description": "The date of the operation that was performed.",
"datatype": {
"base": "date",
"format": "M/d/yyyy"
}
}

Ie, it is definitely respec that adds both. But one would expect that
changing the style sheet would not lead to such differences anyway...

—
Reply to this email directly or view it on GitHub
#26 (comment).

Shane McCarron
[email protected]

[fantasai]

While I can work around this ReSpec issue in the style sheet sort-of (by replacing all occurrences of
.example' with ':not(.example) > .example', which will catch most cases of this ReSpec output), it does seem redundant to me to have the example class on both elements. I would prefer that ReSpec remove the nested 'example' class. On the off chance you need to style PRE blocks inside examples specially, it's very easy to do with '.example pre'.

Let me know what you think.

[halindrome]

I addressed this in my support for your stylesheets.

On Mon, Nov 30, 2015 at 1:55 PM, fantasai [email protected] wrote:

While I can work around this ReSpec issue in the style sheet sort-of (by
replacing all occurrences of
.example' with ':not(.example) > .example', which will catch most cases of
this ReSpec output), it does seem redundant to me to have the example class
on both elements. I would prefer that ReSpec remove the nested 'example'
class. On the off chance you need to style

blocks inside examples specially, it's very easy to do with '.example pre'.

Let me know what you think.

—
Reply to this email directly or view it on GitHub
#26 (comment).

Shane McCarron
[email protected]

[fantasai]

Excellent. I'll close the issue then.