Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

katex plugin broken with more recent version of katex #1203

Open
baldurmen opened this issue Jan 21, 2022 · 1 comment
Open

katex plugin broken with more recent version of katex #1203

baldurmen opened this issue Jan 21, 2022 · 1 comment

Comments

@baldurmen
Copy link
Contributor

Hi,

It seems using more recent versions of katex breaks the katex plugin in glowing-bear. You pinned 0.5.1 (which is quite old, it was released on 2015-09-01), but trying with either 0.10.2 (currently in Debian unstable) or 0.13.11 (Debian experimental) fails to render anything.

With 0.10.2 from Cloudflare, I get:

Uncaught TypeError: o.a is undefined
    l http://0.0.0.0:8000/js/auto-render.js:1
    e http://0.0.0.0:8000/js/auto-render.js:1
    default http://0.0.0.0:8000/js/auto-render.js:1
    <anonymous> http://0.0.0.0:8000/min.js:1
    setTimeout handler* http://0.0.0.0:8000/min.js:1
    l http://0.0.0.0:8000/min.js:1
    l http://0.0.0.0:8000/min.js:1
    <anonymous> http://0.0.0.0:8000/min.js:1
    Angular 4
        fn
        ngBindHtmlWatchAction
        $digest
        $apply
    a http://0.0.0.0:8000/min.js:1
    onmessage http://0.0.0.0:8000/min.js:1
    connect http://0.0.0.0:8000/min.js:1
    i http://0.0.0.0:8000/min.js:1
    connect http://0.0.0.0:8000/min.js:1
    Angular 42
        fn
        callback
        $eval
        $apply
        ngEventHandler
        defaultHandlerWrapper
        eventHandler
        addHandler
        jqLiteOn
        name
        ngEventHandler
        bind
        invokeLinkFn
        nodeLinkFn
        compositeLinkFn
        nodeLinkFn
        compositeLinkFn
        compositeLinkFn
        compositeLinkFn
        compositeLinkFn
        compositeLinkFn
        nodeLinkFn
        compositeLinkFn
        nodeLinkFn
        compositeLinkFn
        compositeLinkFn
        publicLinkFn
        bootstrapApply
        $eval
        $apply
        bootstrapApply
        invoke
        doBootstrap
        bootstrap
        angularInit
        <anonymous>
        trigger
        jqLiteReady
        JQLite
        JQLite
        <anonymous>
        <anonymous>
auto-render.js:1:2408

With 0.13.11, also from Cloudflare:

    l http://0.0.0.0:8000/js/auto-render.js:1
    e http://0.0.0.0:8000/js/auto-render.js:1
    s http://0.0.0.0:8000/js/auto-render.js:1
    <anonymous> http://0.0.0.0:8000/min.js:1
    setTimeout handler* http://0.0.0.0:8000/min.js:1
    l http://0.0.0.0:8000/min.js:1
    l http://0.0.0.0:8000/min.js:1
    <anonymous> http://0.0.0.0:8000/min.js:1
    Angular 5
        fn
        oneTimeWatch
        expressionInputsWatch
        $digest
        $apply
    a http://0.0.0.0:8000/min.js:1
    onmessage http://0.0.0.0:8000/min.js:1
    connect http://0.0.0.0:8000/min.js:1
    i http://0.0.0.0:8000/min.js:1
    connect http://0.0.0.0:8000/min.js:1
    Angular 42
        fn
        callback
        $eval
        $apply
        ngEventHandler
        defaultHandlerWrapper
        eventHandler
        addHandler
        jqLiteOn
        name
        ngEventHandler
        bind
        invokeLinkFn
        nodeLinkFn
        compositeLinkFn
        nodeLinkFn
        compositeLinkFn
        compositeLinkFn
        compositeLinkFn
        compositeLinkFn
        compositeLinkFn
        nodeLinkFn
        compositeLinkFn
        nodeLinkFn
        compositeLinkFn
        compositeLinkFn
        publicLinkFn
        bootstrapApply
        $eval
        $apply
        bootstrapApply
        invoke
        doBootstrap
        bootstrap
        angularInit
        <anonymous>
        trigger
        jqLiteReady
        JQLite
        JQLite
        <anonymous>
        <anonymous>
auto-render.js:1:1987

This is a pretty minor bug (I don't use that feature), but I thought you might want to know.

@lorenzhs
Copy link
Member

lorenzhs commented Feb 1, 2022

Thanks - if you want to fix it I'll be happy to accept a pull request but otherwise I guess we'll stick with the old version if it works ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants