Hmm... do you have some sort of screen reader or accessibility feature, plugin or setting turned on? Because looking at the source: <a class="sr-only gl-accessibility" href="#content-body"...
Hmm... do you have some sort of screen reader or accessibility feature, plugin or setting turned on? Because looking at the source:
<a class="sr-only gl-accessibility" href="#content-body" tabindex="1">Skip to content</a>
'sr-only gl-accesibility' presumably means ''screeen reader only, gitlab accessibility' so if you're seeing that 'Skip to Content' at the top then I assume gitlab thinks you're look at the site with a screen reader since it's not visible otherwise.
Edit: Either that or the CSS file simply failed to load for you (or was blocked by something on your end like an adblocker) since when I disable the primary Gitlab CSS file the site looks exactly the same for me as it does in your screenshot there.
The topic is not locked, just removed... probably because it's not really relevant to ~comp and there is no ~help or ~techsupport yet. It's fine though, I don't mind helping regardless. And if the...
The topic is not locked, just removed... probably because it's not really relevant to ~comp and there is no ~help or ~techsupport yet. It's fine though, I don't mind helping regardless. And if the issue fixed itself, my guess would be that for whatever reason the CSS file just failed to load for you. It happens sometimes with CDNs if the CSS file is coming from a different server than the HTML and times out, or if your local cache of the CSS somehow got corrupted/deleted, or ... a million other reasons. CSS failing to load is a pretty common error across the web.
yeah, and pretty boring, cause today websites are not made to work without css :/ It seems like the problem was decentraleyes, maybe it corruped something on local storage. And yeah, we really...
yeah, and pretty boring, cause today websites are not made to work without css :/
It seems like the problem was decentraleyes, maybe it corruped something on local storage.
And yeah, we really need ~help or ~techsupport
(btw, as a side question, is there any way to tag other users? nvm, it is on an ~tildes.oficial post)
Not yet, but it's in the pipeline. Crius' Tildes Extended supports user tagging now though, which is what I am currently using until that feature is added to the site. edit: Oh, by 'tag other...
(btw, as a side question, is there any way to tag other users?)
Not yet, but it's in the pipeline. Crius' Tildes Extended supports user tagging now though, which is what I am currently using until that feature is added to the site.
edit: Oh, by 'tag other users' did you mean name mention notifications? Yeah, you just put an @ before the username to notify the person you mentioned them... like so @alexandre9099
Working for me as well, and I don't see any complaints on Twitter (lots of angry people on Twitter is usually an easy way to check if something's down). I'm going to remove this, since there isn't...
Working for me as well, and I don't see any complaints on Twitter (lots of angry people on Twitter is usually an easy way to check if something's down). I'm going to remove this, since there isn't really any discussion value.
Working just fine for me... I just added some labels to an issue on the Tildes repo.
maybe it was mine :D (about the OK button)
For me it shows like this https://i.imgur.com/Oyfr2nQ.png
Hmm... do you have some sort of screen reader or accessibility feature, plugin or setting turned on? Because looking at the source:
<a class="sr-only gl-accessibility" href="#content-body" tabindex="1">Skip to content</a>'sr-only gl-accesibility' presumably means ''screeen reader only, gitlab accessibility' so if you're seeing that 'Skip to Content' at the top then I assume gitlab thinks you're look at the site with a screen reader since it's not visible otherwise.
Edit: Either that or the CSS file simply failed to load for you (or was blocked by something on your end like an adblocker) since when I disable the primary Gitlab CSS file the site looks exactly the same for me as it does in your screenshot there.
strange, now on opera it loads, a while ago it loaded the same on firefox and opera, anyway, pretty strange.
The post is already locked/hidden
The topic is not locked, just removed... probably because it's not really relevant to ~comp and there is no ~help or ~techsupport yet. It's fine though, I don't mind helping regardless. And if the issue fixed itself, my guess would be that for whatever reason the CSS file just failed to load for you. It happens sometimes with CDNs if the CSS file is coming from a different server than the HTML and times out, or if your local cache of the CSS somehow got corrupted/deleted, or ... a million other reasons. CSS failing to load is a pretty common error across the web.
yeah, and pretty boring, cause today websites are not made to work without css :/
It seems like the problem was decentraleyes, maybe it corruped something on local storage.
And yeah, we really need ~help or ~techsupport
(
btw, as a side question, is there any way to tag other users?nvm, it is on an ~tildes.oficial post)Not yet, but it's in the pipeline. Crius' Tildes Extended supports user tagging now though, which is what I am currently using until that feature is added to the site.
edit: Oh, by 'tag other users' did you mean name mention notifications? Yeah, you just put an @ before the username to notify the person you mentioned them... like so @alexandre9099
Yeah, i saw that :) thanks anyway, but the private tag thing would also be nice ;)
Working for me as well, and I don't see any complaints on Twitter (lots of angry people on Twitter is usually an easy way to check if something's down). I'm going to remove this, since there isn't really any discussion value.
i see, thanks anyway, maybe it's some routing problem :/