This would be useful for discussions about design, specifically I wished for this feature while reviewing D25491: Improve contrast of Links in Dark Mode

This D25540: Add PhutilRemarkupHexColorCodeRule, a new remarkup rule to format color codes should be ready to merge now, if someone wouldn't mind reviewing it.

Well, you know what would be next level for a dev? If (s)he clicks on it, the color is copied to the clipboard. We can't use this behavior, because behaviors loose their state in the remarkup cache...

I'm somehow even more inclined to propose to base this feature on a new custom parser, like cowsay {{{ asd }}}

So, we could have something like color {{{ #0000ff }}}. That would be parser-safe, and it would also allow to support some interesting unexpected options in the future.

Or wrap a text with a background color - (something like What if I can change the background color here (and no italics)?)

I think I'm essentially echoing what valerio.bozzolan said, but since I'm not sure if I get their idea correctly... :P

EDIT: This was already reported and resolved in T15802: Regression: HTML entities rendered as plain text in config option descriptions, I'm keeping the comment just to track this.

Hi, D25540: Add PhutilRemarkupHexColorCodeRule, a new remarkup rule to format color codes is breaking formatting for me.
When I add a task comment containing an apostrophe (Like Let's Encrypt), the comment is rendered in the browser as Let's Encrypt.. The comment is stored correctly in the database. This is a fresh deployment of Phorge.

When I comment these two lines, rendering to html reverts back to normal:

diff --git a/src/__phutil_library_map__.php b/src/__phutil_library_map__.php
index 17b1e837a6..3b4a28219d 100644
--- a/src/__phutil_library_map__.php
+++ b/src/__phutil_library_map__.php
@@ -12638,7 +12638,7 @@ phutil_register_library_map(array(
     'PhutilRemarkupEscapeRemarkupRule' => 'PhutilRemarkupRule',
     'PhutilRemarkupEvalRule' => 'PhutilRemarkupRule',
     'PhutilRemarkupHeaderBlockRule' => 'PhutilRemarkupBlockRule',
-    'PhutilRemarkupHexColorCodeRule' => 'PhabricatorRemarkupCustomInlineRule',
+    // 'PhutilRemarkupHexColorCodeRule' => 'PhabricatorRemarkupCustomInlineRule',
     'PhutilRemarkupHighlightRule' => 'PhutilRemarkupRule',
     'PhutilRemarkupHorizontalRuleBlockRule' => 'PhutilRemarkupBlockRule',
     'PhutilRemarkupHyperlinkEngineExtension' => 'Phobject',
diff --git a/src/infrastructure/markup/PhabricatorMarkupEngine.php b/src/infrastructure/markup/PhabricatorMarkupEngine.php
index 84503048d0..df3880644c 100644
--- a/src/infrastructure/markup/PhabricatorMarkupEngine.php
+++ b/src/infrastructure/markup/PhabricatorMarkupEngine.php
@@ -526,7 +526,7 @@ final class PhabricatorMarkupEngine extends Phobject {
     $rules[] = new PhutilRemarkupEscapeRemarkupRule();
     $rules[] = new PhutilRemarkupEvalRule();
     $rules[] = new PhutilRemarkupMonospaceRule();
-    $rules[] = new PhutilRemarkupHexColorCodeRule();
+    // $rules[] = new PhutilRemarkupHexColorCodeRule();

     $rules[] = new PhutilRemarkupDocumentLinkRule();
     $rules[] = new PhabricatorNavigationRemarkupRule();

Yet it doesn't explain, why is it misbehaving like this.

@zajdee have you already tried to update to latest master? After 6ab2b56a1a4a6 I mean. Thanks for this confirmation

@valerio.bozzolan yes, just now. I have only realized that there is a fix already after opening the ticket raised as a concern. Hadn't checked this in the past few days, so here I am, finally with my account approved and the issue is fixed. Thank you. :)

Anyway, even with this fix, for some reasons I can't still use this feature with a comment like {#0000ff} in my local installation 🤔 I'm confused since the unit test works.

Thanks again @20after4 for the efforts.

I followed "BE BOLD" and I've expanded a bit the description of this Task. Still thank you, and feel free to revert if you think it's too much :D thanks my friend

I was unaware of #0969DA syntax from github/gitlab. I'm not sure if I like that syntax better than {} but I am generally in favor of using the same syntax as other systems in order to converge towards defacto standardization.

In T15744#18236, @20after4 wrote:

I was unaware of `#0969DA` syntax from github/gitlab.

Ok I just tried it in a README context on github and it's not working for me. It just renders the color code in a grey background monospace, the same as current Phorge behavior. What am I missing?

I think GitHub allows that syntax only in comments 🤔

https://stackoverflow.com/a/60783169/3451846

Can reproduce here:

https://github.com/valerio-bozzolan/Test/issues/1