You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a slightly modified index.html page which includes my custom CSS styles and text changes. With the most recent update I ran into an issue with the index template where #url was undefined causing a fatal JavaScript error.
To keep things simple and to not make changes to main.js I just set the color of the URL div to match the background color which works. I think I could also use visibility:hidden instead
Overall, I do like the new changes providing more information but wondering if we should wrap some of the getElementById statements in a if type !== undefined) checks. If so, which ones?
The main one the effects the layout I've found is #URL so that's why I'm specifically mentioning that one.
The text was updated successfully, but these errors were encountered:
I can certainly implement this, as it's a pretty quick fix. Maybe it could be an idea to allow some kind of custom HTML setup, but right now I have no idea whatsoever on how to practically implement that.
I use a slightly modified
index.html
page which includes my custom CSS styles and text changes. With the most recent update I ran into an issue with theindex
template where#url
was undefined causing a fatal JavaScript error.I tracked this down to
document.getElementById("url").textContent = url;
inmain.js
https://github.com/bilde2910/Hauk/blob/master/frontend/main.js#L215
To keep things simple and to not make changes to
main.js
I just set the color of theURL
div to match the background color which works. I think I could also usevisibility:hidden
insteadOverall, I do like the new changes providing more information but wondering if we should wrap some of the
getElementById
statements in aif type !== undefined)
checks. If so, which ones?The main one the effects the layout I've found is
#URL
so that's why I'm specifically mentioning that one.The text was updated successfully, but these errors were encountered: