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

Comments on Interface for showing changes in the history is not very discoverable

Parent

Interface for showing changes in the history is not very discoverable

+2
−0

It took me quite a while to discover how to see what was changed in an edit.

Some visual clue on how to get it would be a good idea, I think.

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?

0 comment threads

Post
+3
−0

So this is an artifact of me not testing across multiple browsers. In Chrome, the <summary> element (which the history type, username, and timestamp are contained in) automatically inserts an arrow for you, exactly as luap42 suggested. Looking now in Firefox, it doesn't.

I'll have a look at how possible it is to add an indicator just for Firefox (and any others that don't auto-insert one).

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

1 comment thread

General comments (2 comments)
General comments
luap42‭ wrote almost 5 years ago

That's strange. This code: <details><summary>y</summary>x</details> works perfectly fine in a blank page in Firefox. It seems to be caused by Bootstrap applying display: block; to the summary element.

ArtOfCode‭ wrote almost 5 years ago

That's annoying, @luap42. Ah well, no matter - fixed now, I added some FF-specific CSS.