Increase drawer wide to support Grammarly browser extension #53

New issue

Closed

opened 2019-02-08 10:31:13 +00:00 by sukinoverse · 1 comment

sukinoverse commented

2019-02-08 10:31:13 +00:00

Member

From Grammarly official website,
it required the following condition on the message box.

$0.clientWidth > 301 && $0.clientHeight > 38

Reference: https://support.grammarly.com/hc/en-us/articles/115000090392-I-do-not-see-the-G-icon-on-a-certain-web-page-or-in-a-certain-text-field-but-see-it-on-other-web-pages-

Anyway, the latest Mastodon-FE makes Grammarly's browser extension not working anymore.

Can we adjust it a bit to make Grammarly working correctly?

Best regards

From Grammarly official website, it required the following condition on the message box. `$0.clientWidth > 301 && $0.clientHeight > 38` Reference: https://support.grammarly.com/hc/en-us/articles/115000090392-I-do-not-see-the-G-icon-on-a-certain-web-page-or-in-a-certain-text-field-but-see-it-on-other-web-pages- --- Anyway, the latest Mastodon-FE makes Grammarly's browser extension not working anymore. Can we adjust it a bit to make Grammarly working correctly? Best regards

lanodan commented

2019-04-04 06:16:11 +00:00

Owner

amount of text that can fit/is present
the overall area size (height*width > whatever)

I do not really like closing an issue for this kind of extension but honestly I think it’s more like their bug to fix.

I looked at it and it’s making the compose column quite bigger for some reason and honestly while I can understand why they need to filter the textareas, I think their math should be something like: - amount of text that can fit/is present - the overall area size (`height*width > whatever`) I do not really like closing an issue for this kind of extension but honestly I think it’s more like their bug to fix.