Test style for debugging conversion to userscript

It was brought to my attention that some style stopped working as userscript…

코드가 업데이트된 버전 목록입니다. 모든 버전 보기

  • v45.0.0 2024-02-09

    Just moved the (empty) comment back from within the document block before it, to confirm it breaks the conversion to JS.

  • v44.0.0 2024-02-09

    ok, so removing comment before local part fixes it. so if the comment was not before, but inside the local part....

  • v43.0.0 2024-02-09

    works with first comment removed. returning it and removing the second comment.

  • v42.0.0 2024-02-09

    still borked, extra blank lines make no difference. removing first comment.

  • v41.0.0 2024-02-09

    yup, without comments it worked. returning them back but adding extra blank lines.

  • v40.0.0 2024-02-09

    still borked. removing comments yet again. expecting it to work.

  • v39.0.0 2024-02-09

    still borked. making comments totally empty

  • v38.0.0 2024-02-09

    still borked. removing content of comments, so they contain only two returns.

  • v37.0.0 2024-02-09

    still borked. removing some linebreaks to have it even shorter.

  • v36.0.0 2024-02-09

    So the problem occurs only when there are two comments, one before global and one before local part. Returning v32 but changing * to el in global.

  • v35.0.0 2024-02-09

    was OK. returning first and removing second comment

  • v34.0.0 2024-02-09

    yup, it worked. removing only first comment from 32.

  • v33.0.0 2024-02-09

    still borked. omg. removing comments, expecting it will work again.

  • v32.0.0 2024-02-09

    still borked. changing *:not(#a) to *

  • v31.0.0 2024-02-09

    borked. changing *:not(#a) to *:not(#a)

  • v30.0.0 2024-02-09

    still borked. simplifying rules further.

  • v29.0.0 2024-02-09

    was borked, simplify more

  • v28.0.0 2024-02-09

    was borked. simplifying global rule a bit.

  • v27.0.0 2024-02-09

    was OK, both comments back, effectively restoring v32. should be borked.

  • v26.0.0 2024-02-09

    was OK. comment before global part back, comment before local part out

  • v25.0.0 2024-02-09

    was OK. comment before local part back

  • v24.0.0 2024-02-09

    was borked. comments out.

  • v23.0.0 2024-02-09

    was OK, first comment and rule back, rest of global part out

  • v22.0.0 2024-02-09

    first comment and rule out

  • v21.0.0 2024-02-09

    oops, last borked was 16, what am I doing here. restoring again.

  • v19.0.0 2024-02-09

    actually previous versions were ok, restoring v15

  • v18.0.0 2024-02-09

    still broken. reducing global part to bare bones, no nesting this time

  • v17.0.0 2024-02-09

    v16 broken, simplifying global part a bit

  • v16.0.0 2024-02-09

    still ok. returning comment before local part.

  • v15.0.0 2024-02-09

    v14 was OK. returning first root-level comment.

  • v14.0.0 2024-02-09

    Removed root-level comments.

  • v13.0.0 2024-02-09

    v12 Still borked. Now removed only some insignificant white-space.

  • v12.0.0 2024-02-09

    v11, still borked, simplifying non-global part to bare bones. (that is the part that propagated to JS.)

  • v11.0.0 2024-02-09

    hm, removing comments apparently fixed it. restoring v9 and removing just a bit from last rule

  • v10.0.0 2024-02-09

    ...removed comments...

  • v9.0.0 2024-02-09

    removed at-layer

  • v8.0.0 2024-02-09

    Ha, v.7 borked. Simplify it now, if it keeps breaking...

  • v7.0.0 2024-02-09

    1/3 "local" parts from the other style

  • v6.0.0 2024-02-09

    Entire global part copypasted from the problematic style

  • v5.0.0 2024-02-09

    So maybe at-layer?

  • v4.0.0 2024-02-09

    Local part with nesting

  • v3.0.0 2024-02-09

    No nesting, but slightly insane selector.

  • v2.0.0 2024-02-09

    Changed to the global part to use CSS nesting selecor (&) to see if it breaks conversion. (So far was OK.)

  • v1.0.0 2024-02-09