Maybe someday this will be easier; https://lists.w3.org/Archives/Public/www-style/2016Mar/0370.html

I'll get back to you

Well

I think the pros and cons are something like:

oh man these crack me up.

Haha, sorry I think this might be a good JS learning side project for me on the weekends if I have free time.

I think we should just use actual emoji for this, not sprite sheets?

In D17238#205025, @epriestley wrote:

Yep, go for it.

This is extremely old and it's not clear to me which bad cases remain -- I can't immediately find any by fiddling. If any do remain, they haven't turned up again in about two years. If you're still seeing issues, feel free to file a new task with a modern test case.

• Systems integrated with Doorkeeper (JIRA, Asana, some prototype GitHub support) already get URIs marked up.
• The current JIRA integration does cover JIRA URIs in all remarkup systems, including Phriction and Maniphest, although you can not link to multiple JIRA installs until T6703, and you must use full URIs (if you use JIRA-123, it's possible that multiple linked installs have project namespaces called "JIRA"). It's possible we'll support this more naturally in the future, but not until after T6703, which is a very low priority.
• Custom markup rules already supported (see P1157, P1209 for some examples), although you're on your own to write them. These are probably the best fit for your use case.
• I believe needs for this sort of thing are often very specialized, so I do not currently plan to add any kind of generic, configurable remarkup rule that just matches arbitrary regexps against stuff and links them. You could write such a rule as an extension. One caveat to this is that we currently have bugtraq.url and bugtraq.logregex, which sort of work like this, except in a bad way. I'd like to remove them in the future, but there's an outside possibility that we'll replace them with a more flexible system like the one you describe.

Richer integration would likely happen sooner than something like this, simply because it's something we frequently get asked for and benefits a large group of installs.

I updated the summary to hopefully make the problem description more clear, and to add an additional problem which I encountered on one vendor's custom made bug tracker, where their search was returning URLs that were only temporarily valid in the session that the search was done in.

Can you please check out Contributing Feature Requests and Describing Root Problems. We don't accept feature requests of this nature unfortunately without understanding the core problem. For example, external systems in the future could be fully integrated automatically with Phabricator, and make the need for special Remarkup pointless. We're not interested in things that are hypothetically cool or useful, and don't have the bandwidth to pursue specialized requests that can already be accomplished with a small plugin.

You can do this yourself today with a Remarkup Extension. Parse specific URL patterns in remarkup and return them looking however you want.

You are right, I also can't reproduce it on the Phacility instance. I really don't know what do do next ^^

Please take the time to try to reproduce the issue on a Phacility instance, and report back if you can. We have not been able to reproduce the issue with these set up steps. Reproduction steps must includes everything we need to review and fix the issue locally.

Thank you much, @chad

Is a pretty basic one, simple regex / replace. Write your CSS inline.

Yeah, that seems like a valid solution, however the spoiler in question is still visible, and could get glimpsed at before reading the warning. It'll have to do for now.

Putting something like a header maybe could help in the meantime?

We don't consider the fact that feature is missing, and would be used, a root problem. Something along the lines of understanding how your company was operationally impacted by seeing/hiding a spoiler would be helpful.

Strange, I read the Contributing Feature Requests documentation prior to submission, and I figured I'd described the root problem as having revealed content that is context-sensitive with my example of a TV series spoiler. There are potentially more uses outside of TV series spoilers, and I don't think it's any less valid than something like Macros.

See Contributing Feature Requests for what information is required in a valid feature request. Specifically this request lacks a root problem and doesn't seem to be about coding / product development. We also can't enforce people knowing when to use such tags, so even having them doesn't really solve the problem of tv show spoilers.

Pretty sure this works as intended

Look at how much engagement we're generating!

comments

more

need

still

I would edit my comment to put a paragraph of text above the autoplay audio, but newsfeed caches the old comment. :3

I think we can safely conclude that autoplay audio in feed is an effective mechanism for disseminating important information.

Sure seems to be a lot of activity that generates feed stories on this task!

@epriestley FYI

• Prototype applications must be enabled.
• security.outbound-blacklist must not blacklist the target server (build servers may be on an internal network and on the default blacklist).
• The link protocol must be "http" or "https".
• You must not have exceeded your fetch quota for the last hour.
• You must have file storage configured.
• The image MIME type must be part of files.image-mime-types and files.viewable-mime-types.
• The Phabricator server must be able to make outbound requests on the network.

In T4190#199608, @epriestley wrote:

(But note that it's cached for a trillion years, so it won't work for build status.)

Does the {img } thing work yet? I've been trying to use it locally but have not been able to get it to actually show an image. This would be super useful for us to be able to show the build status on a remarkup page (like the README.MD of our repo, for example). Thanks.

For reference, http://phacility.com/ is a Phabricator application itself, so think all the tools are available.

I presume you meant to ask this question in Ponder, otherwise please see Contributing Feature Requests for what information is required in a feature request. Generally, we do not provide support for building applications/plugins/extensions against Phabricator.

T11747 wants a more advanced version of this (reviewing diffs between rendered documents), although the specific document type it wants (IPython notebooks) is likely very complex to render.

What about display images set like this?

(I'll follow up on this once I have a chance to bang on it a bit, but I want to try to finish up the RRULE stuff while it's still somewhat fresh in my mind.)

To actually add a remarkup rule, the basics are simple:

I think this didn't actually get handled in T10262, but should be doable now.

Did this ever actually work? it looks like we're still embedding links:

On the cache:

In this case, use the AphrontWriteGuard::beginScopedUnguardedWrites() method to surround the block -- you can grep for usage, but it will look like this:

I've got the endpoint and controller set up, but I get the following error when I call PhabricatorFile::newFromFileDownload:

Alright I've been able to narrow this down a little bit more. There's some error with how external/pear-figlet/Text/Figlet.php is smushing characters. Specifically lines 339-362 as well as the _rep($r) function. The equivalent function in the C code is here. I haven't been able to find an obvious discrepancy, but I suspect there's a subtle difference in how one of the regex functions is handling things or an error in one of the regexes themselves. This error also occurs with backticks and double-quotes:

Ohhh nice, thank you I missed that
=C124

And you can technically:

Oh, right. That works, but I think isn't documented:

It's an off-case for sure. We have a ton of data identifiers which all end with an equals-sign and a couple letters/numbers, which we abbreviate when referring to the datasets. I was actually trying to render the equals sign as part of the nav sequence and not just C124.

We could conceivably special-case this since setting an empty attribute to a value isn't meaningful, I suppose.

.remarkup-code td span

Good to know. :) I think that embedding panels is enough. It did not occur to me that I can do that, much cool. :)

I think if you really want the table layout you can extend and build your own Dashboard Panel Redererer, then wire up to any query and embed away.

Good catch, thanks.

You can embed Dashboard Panels already today into other documents. These are based on any query you build in any supporting application. Beyond that you will need to wait for Facts for something more data-like.