# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 10
# self = https://watcher.sour.is/conv/y463i3a
@darch, the “Settings” screen has issues as well. I can screenshot it and twtxt about it, but it is easier to see. Click on “Settings” and see the alignment of the three blue buttons, and width in comparison with the rest of the page. This on both, desktop, and mobile.
@bender please provide screenshot with comments. Preferably as an issue on the gitea for yarnd
@darch on “Timeline”, inspect any of the <article id> tags. Their computed width is 834px. Now go to “Settings”, and inspect any <article>. Their computed width is 802px.

The way I see it, this is what causing this specific problem (the commented out padding):


.tabs .tab {
    order: 99;
    width: 100%;
    display: none;
    /* padding: 1rem; */
}


Anyway, I am not a frontend designer.
@bender .tabs .tab are not appied to <article id> or <article id> so i still dont "see" the issue.
> please provide screenshot with comments. Preferably as an issue on the gitea for yarnd
@darch



Versus:

The .tabs .tab classes are applied to a <div> on “Settings". That padding is pushing the <article> tabs. What do you use for content creation, Microsoft Windows?
@bender ah okay, so nothing to do with the horizontal scroll. Thanks for notices and bringing to attention
@bender ah okay, so nothing to do with the horizontal scroll
@darch where did I mention scrolling on this yarn?
@bender you did not. i just didn't notice it was not the same tread.