𝓒𝓱𝓻𝓲𝓼 wrote the following post Thu, 17 Sep 2026 12:01:21 +0200

Submitted ⁨⁨3⁩ ⁨days⁩ ago⁩ by ⁨development@hubzilla.org [bot]⁩ to ⁨development@hubzilla.org⁩

𝓒𝓱𝓻𝓲𝓼𝓒𝓱𝓻𝓲𝓼 wrote the following post Thu, 17 Sep 2026 12:01:21 +0200

MD wikis do except some HTML code but entries like target="_blank" will be deleted because of include/text.php.

Is this wanted ?

Would it be ok to uncomment in include/text.php line 194 `$config->set('HTML.TargetBlank', true);` for good in core ?

original

Comments

Sort:hotnew top

mario@hub.somaton.com ⁨2⁩ ⁨days⁩ ago
https://framagit.org/hubzilla/addons/-/commit/70621a969c28e73894eb8927e9dbcf240a4b79f5

In future please do not use this forum for bugreports or feature requests. Thanks!
original
- chris@im.allmendenetz.de ⁨2⁩ ⁨days⁩ ago
  Mario Vavti wrote:
  framagit.org/hubzilla/addons/-/commit/70621a969c28…
  thank you very much
  original
- chris@im.allmendenetz.de ⁨2⁩ ⁨days⁩ ago
  @Mario Vavti well , after all it was not really a bug or a feature request
  original
mario@hub.somaton.com ⁨3⁩ ⁨days⁩ ago
Just for the record, the actual issue here seems to be that having code permission does not omit HTML purifier in this case.
original
- pepecyb@hub.hubzilla.hu@hub.hubzilla.hu ⁨3⁩ ⁨days⁩ ago
  Personally(!), I’m not a fan of being treated like a child – after all, I’m already a “grown-up”. What I mean is: in principle, it’s up to the author of the content to prevent the problem with rel="noopener noreferrer".
  
  So apparently, the code authorisation is meant to prevent the use of the Purifier – have I got that right, @mario@hub.somaton.com ? At least on the wiki, that doesn’t seem to be working. If the code authorisation could allow ‘target’, it would effectively serve as proof of being ‘of age’, which would then make guardianship regarding target="_blank" unnecessary. 😉
  original
pepecyb@hub.hubzilla.hu@hub.hubzilla.hu ⁨3⁩ ⁨days⁩ ago
I can’t see why not. Or could there be any side effects?

@mario@hub.somaton.com @Harald Eilertsen
original
- harald@hub.volse.no@hub.volse.no ⁨3⁩ ⁨days⁩ ago
  There used to be an issue where the newly opened tab/window could redirect the original tab/window to another URL, potentially a malicious one.
  
  This seems to no longer be the case, though, but I haven't come across any information about when this was fixed.
  original