Wikimedia parser handling relative paths differently

  • Pekka

    (@pekkagaiser)


    4 years, 7 months ago

    Just updated from 1.8.0 to 1.9.3 and it appears the Wikimedia parser that is being used since 1.9 is handling relative paths differently from the Oyejorge one that was used in previous versions.

    Got a LESS file:
    /less/index.less

    That file @imports another LESS file:
    /less/webfonts/webfonts.less

    In that file, a web font is embedded using a relative path, like so: 

    @font-face {
  font-family: "MyFontName-Regular";
  src: url('mywebfont/font.woff2') format('woff2'), url('mywebfont/font.woff') format('woff');
}

    The Oyejorge parser used to resolve the path in the web font relative to the current LESS file:

    /less/webfonts/mywebfont/font.woff2

    The Wikimedia parser resolves the path in the web font relative to the main LESS file:

    /less/mywebfont/font.woff2

    Not sure which behaviour is the desired one. Rolling back to 1.8.0 for now (wondering why that isn’t possible directly from the archive?)

    • This topic was modified 4 years, 7 months ago by Pekka.

The topic ‘Wikimedia parser handling relative paths differently’ is closed to new replies.