Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken websites #14

Open
2 of 4 tasks
echebbi opened this issue Jan 20, 2018 · 3 comments
Open
2 of 4 tasks

Broken websites #14

echebbi opened this issue Jan 20, 2018 · 3 comments

Comments

@echebbi
Copy link
Contributor

echebbi commented Jan 20, 2018

A reminder of all the websites which are not well displayed by Shuttle yet:

  • Twitter
  • Spotify
  • Messenger
  • Rocket.Chat

Note: this issue is aimed to be completed later. If a website is checked, it is now supported by Shuttle.

@Atomy9
Copy link

Atomy9 commented May 23, 2018

Rocket.Chat works but has a few broken features : can't add reactions, can't reply, can't click on links (although I believe this problem occurs on every website when using Shuttle.

Is there any way to fix these rocket chat problems ? It's pretty much the only service I use with shuttle and it would be perfect with these.

@echebbi
Copy link
Contributor Author

echebbi commented May 26, 2018

Hello @Atomy9 !

Unfortunately, we do not have many time to solve this problem for the moment. We will work on a fix as soon as possible.

If you have the knowledge to solve the issue, feel free to submit a PR. The adapter.js file makes possible to dynamically change the content of a web page according to its URL.

I do not use Rocket.Chat so I am unable to test right now, but the fix may be as simple as injecting or replacing some CSS. Do you know if Rocket.Chat works well from a smartphone ?

@Atomy9
Copy link

Atomy9 commented May 27, 2018

Hello @KazeJiyu

Thanks for the reply. I am not that familiar with coding, but I know a little bit of javascript. Looking at your adapter.js, I'm not sure the solution for rocket.chat would be as easy messenger for example. Because rocket.chat is a self-hosted solution, which implies that each instance is using a different URL. So the "url.startsWith(...)" wouldn't work I think.

Oh and yes, it works just fine on a smartphone because most interactions with messages are done by long pressing. If searched for a way to simulator a smartphone long press on Windows but without success...
Hope that helps, and that someday you'll have the time to fix this. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants