#1361 Unresponsive screen rendering by mod_conversejs

Reporter workrock
Owner Zash
Created
Updated
Stars ★ (1)
Tags
  • Priority-Medium
  • Type-Defect
  • Status-Fixed
  • Component-Community
  1. workrock on

    The current mod_conversejs plugin renders an unresponsive html page. Although its not a serious issue it left me puzzled as to why this was happening. The problem in the end was a simple one. Default conversejs page generated by mod_conversejs did not have a meta viewport tag. There's an easy solution using the conversejs_tag option. I simply added a meta tag to the table. <meta name="viewport" content="width=device-width, initial-scale=1.0"/> Below is the full conversejs_tags table:- ``` conversejs_tags = { -- Load custom CSS -- [[<link rel="stylesheet" href="https://example.org/css/custom.css">]]; [[<meta name="viewport" content="width=device-width, initial-scale=1.0"/>]]; -- Load libsignal-protocol.js for OMEMO support (GPLv3; be aware of licence implications) [[<script src="assets/js/libsignal-protocol.min.js"></script>]]; ``` It would be great if either it could be added into the documentation on how to make the screen responsive. Or simply modify the source file to include a viewport tag by default. Its a one line change if I understand correctly. https://hg.prosody.im/prosody-modules/file/4feab7e87675/mod_conversejs/mod_conversejs.lua#l31 Thanks!

  2. workrock on

    Another mod_converse issue on this link https://issues.prosody.im/1362

  3. Zash on

    Done in https://hg.prosody.im/prosody-modules/rev/f32efd448794 I don't think Converse.js works well on small screens, so I'm not sure if this is of any use. IIRC there is a separate view_mode for mobile.

    Changes
    • owner Zash
    • tags Component-Community Status-Fixed

New comment

Not published. Used for spam prevention and optional update notifications.