When printing HTML to the console, differentiate between tag objects and `HTML()` text

Open
#266 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
tooling

Research direction

Start by tracing the console-printing entry point for tag objects and the tagQuery() behavior described in the issue, including the tags produced by shiny::selectInput(). Check how HTML() text and tag objects are currently represented, then add a distinguishable display and tests showing that the output makes non-findable tags apparent.

Written by the indexing model from the issue text.

Description

This is important for tagQuery() as (for example) the <option> tags from shiny::selectInput() can not be found with $find().

This is confusing and unexpected. If the text was grey / italics (or something), then I would have a hint that I can not $find() the tags.

cc @gadenbuie

Dominant language
R
Stars
225
Forks
73
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rstudio/htmltools

All issues in rstudio/htmltools

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.