@icedquinn@silverpill@p@frogzone@nimda For the context, bloat does all the work on the server side and returns the rendered HTML. There is a bit of JavaScript involved, but it's completely optional. You navigate the timelines and other pages by clicking on next/prev links. So, there's no "events" involved here. It might be possible to "grep" through the posts to detect hashtag URLs, but it'd be a bit hacky solution. Parsing the HTML and looking for the links with the "hashtag" class is another solution, but I don't want to do that either.
@frogzone >For top frameset add attribute: cols="36%,*" 36% looks way too wide on a typical 16:9 display >For both framesets border="1" border is not a standard attribute for a frameset, it might work in some browsers, I know it does in Chrome and Firefox, but because it's not part of the standard, I'm not going to use it. >font-size: 14px; px is an absolute value and shouldn't be used for text because it doesn't change when you change the default font size of the browser. >Can everyone see them in their browsers? I can see some of them, but most of them appear as boxes.
None of this really matters if you just want to keep these changes to yourself though. I'm glad you were able to customize it to your liking.
@frogzone@p@p Only the font-size should use relative unit, using px for rest of the things is fine. Actually, most websites still use px for font-size, even bloat used it until the recent redesign. It's more of an accessibility issue than anything. See https://developer.mozilla.org/en-US/docs/Web/CSS/font-size#pixels
@frogzone@icedquinn@silverpill@p@nimda The reason for not having hashtag search is because I don't use hashtags myself and most of the people I follow don't use them either. And no one had asked me for it until now, but now that you asked for it, maybe I'll implement it.
@frogzone@icedquinn@silverpill@p@nimda So I implemented the hashtag search and hashtag timeline, it was pretty straightforward. But there doesn't seem to be an easy way to detect hashtags that are part of a post (required to redirect to the hashtag timeline by clicking on a hashtag). The way bloat handles mentions and emojis is by matching the appropriate URLs provided in the response and then doing a simple string replacement. In case of hashtags, the tags inside the post content have remote URLs, but the actual tags array has the local URLs, so it's not possible to do the matching. I looked at how Pleroma-fe works, turns out, it doesn't do the replacement, but instead handles the click event on the tag and then extracts the tag name from the URL to redirect to the Pleroma-fe's hashtag timeline page.