Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on PSA: question tagging UI apparently now depends on JavaScript from codidact.org

Parent

PSA: question tagging UI apparently now depends on JavaScript from codidact.org

+4
−0

I use Noscript, so Javascript is blocked by default for new domains for me.

As it happens, prior to today I had codidact.com (and jsdelivr.org) whitelisted, but not codidact.org. When I was writing my previous Meta post just now, I found that the tag search/auto-completion (at the bottom of the question form) was not working.

On an instinct, I checked my Noscript settings and discovered that JavaScript from codidact.org was blocked. Upon allowing it and refreshing the page, the tag interface worked again.

Is this split architecture intentional? How long has it worked this way?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

I don't think that's intentional, no. Thanks for the report. (1 comment)
Post
+3
−0

I am not able to reproduce this. I visited the "create post" page with NoScript turned on and this is what I see:

NS shows codidact.com and a few others but not codidact.org

Can you say more about where you saw codidact.org?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

update (3 comments)
update
Karl Knechtel‭ wrote 9 months ago

I see it in the same menu, after the cloudflareinsights.com entry. You should too after trusting codidact.com. However, I am no longer reproducing the rest of the bug: while codidact.com JavaScript is still required to make the widget work (as I would expect), codidact.org JavaScript is not.

Monica Cellio‭ wrote 9 months ago

That's odd. I temporarily trusted codidact.com and refreshed, and codiact.org didn't show up for me. I did this in Firefox, in case that matters. I'm glad to hear that .org JS isn't required, though!

Karl Knechtel‭ wrote 9 months ago

At any rate, it's probably appropriate to close this as no-repro....