Could you disable scrolling on the wrapper without disabling scrolling of the chat itself?
@hoangphuctran93 Did you ever figure out how to call the hamburger menu to open? I want to call the new sidebar to open, which should be the same call.
Though a team member created the component (wasn’t necessarily part of the team when they created it), it’s not official and will not be monitored and updated as much as official ones.
For this kind of component, I think it will benefit from pull requests if someone wants to give it a try to fix the existing issues.
If anyone is using the assigned plugin this URL works:
my/activity/assigned
What do we enter into the box in settings to add a new font awesome icon?
DId anyone manage to get this working? In the wake of the Ai Chatbot function, users might need to be alerted when the bot replies and make the unread messages icon carry a badge as per social media industry standards for UI/UX.
this now breaks the site, not sure why
The original repository received recent updates to fix deprecations and make other improvements. It’s not currently available in @th21 's fork.
Where is the original repository?
You can see any original repository at the top of the topic. Here is what you’re looking for: GitHub - OsamaSayegh/discourse-tab-bar-theme.
Looks great! Do wish there were back/forward buttons.
Is there some style error on the Chat or DM page? Like there seems an empty space there and there is no tab bar option there.
If i created a couple of forks of this and reinstalled them, would it be possible to define which url’s on my site each one loads?
For example
- ‘load/exclude on url: /t/’
- ‘load/exclude on url: /c/’
- ‘load/exclude on url: /c/puppies’
The goal is to creating a tab-bar that changes icons and links for 3 different areas of the site, bringing to users the actions that i want users to take in each area.
I wonder if the Kanban plugin function ‘Display categories’ might have some code that could be repurposed to enable that.
A list of categories where the "Board" button should appear. If left blank, it will be shown everywhere. Use @ to denote the top level view.
Alternatively, perhaps the isHomepage
getter could be modified to check for other pages too?
That’s not possibly by simply installing multiple copies of the component – you’d need to fork the component and modify it to support your use case.
Yes, that’s what i’m suggesting. I’m asking whether that is a sensible route to go and if its likely to work with the lovely component you’ve built.
You know better the needs of your site/community, so if you feel like that would be an improvement for your site or it would solve a problem, you’re certainly more than welcome to fork the code and modify it. That’s the beauty of open source