Skip to content

Drawing notation in wrong location #17

Open
Open
Drawing notation in wrong location#17

Description

@0x213F
0x213F
opened on Dec 28, 2020

Describe the bug
I am rendering multiple RoughNotation elements inline the same component. It looks something like this initially:

<div>
<span>Hello, my name is </span>
<RoughNotation className={styles.Notated}
show={true}
color="red"
type={modification.type}
animate={modification.animate}>
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

When the user interacts with the page, they can add more notations. For example, look at the following:

<div>
<span>Hello, my </span>
<RoughNotation show={true} color="red" type="highlight">
name
</RoughNotation>
<span> is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

When the new notation occurs before the already established notation, it renders fine (no bug). However, when it renders after, it does not render as expected:

<div>
<span>Hello, my name is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to </span>
<RoughNotation show={true} color="red" type="highlight">
meet
</RoughNotation>
<span> you!</span>
</div>

To Reproduce
Steps to reproduce the behavior:

  1. Render one Rough Notation inline
  2. Render a second Rough Notation inline, after the first one
  3. See error
  4. You may keep adding Rough Notations ahead of the last one to continue reproducing.

Expected behavior
(I was able to do this by "filling in" the Rough Notations backwards)

Screen Shot 2020-12-28 at 11 54 14 AM

Screenshots
("Filling in" the Rough Notation forwards, it highlights the first word 3 times in a row)

Screen Shot 2020-12-28 at 11 55 01 AM

Here is what the DOM looks like. I'm posting this as evidence that I didn't accidentally notate the same element 3 times, but instead did it to 3 different intervals.

Screen Shot 2020-12-28 at 12 04 10 PM

Desktop (please complete the following information):

  • OS: macOS
  • Browser Chrome
  • Version 87.0.4280.88

Additional context
Let me know how I can assist with this bug. I am having trouble understanding what the root cause may be. If someone could help point me in the right direction, that would be greatly appreciated!

If this ends up being a bug with a library, I would be happy to work on a PR if someone could give me more context on the fix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    , 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
     blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Drawing notation in wrong location · Issue #17 · linkstrifer/react-rough-notation · GitHub
    Skip to content
    Drawing notation in wrong location #17
    Open
    Open
    Drawing notation in wrong location#17
    Description
    @0x213F
    0x213F
    opened on Dec 28, 2020
    Describe the bug
    
I am rendering multiple RoughNotation elements inline the same component. It looks something like this initially:
    <div>
<span>Hello, my name is </span>
<RoughNotation className={styles.Notated}
show={true}
color="red"
type={modification.type}
animate={modification.animate}>
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

    When the user interacts with the page, they can add more notations. For example, look at the following:
    <div>
<span>Hello, my </span>
<RoughNotation show={true} color="red" type="highlight">
name
</RoughNotation>
<span> is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

    When the new notation occurs before the already established notation, it renders fine (no bug). However, when it renders after, it does not render as expected:
    <div>
<span>Hello, my name is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to </span>
<RoughNotation show={true} color="red" type="highlight">
meet
</RoughNotation>
<span> you!</span>
</div>

    To Reproduce
    
Steps to reproduce the behavior:
    1. Render one Rough Notation inline
    2. Render a second Rough Notation inline, after the first one
    3. See error
    4. You may keep adding Rough Notations ahead of the last one to continue reproducing.
    Expected behavior
    
(I was able to do this by "filling in" the Rough Notations backwards)
    Screen Shot 2020-12-28 at 11 54 14 AM
    Screenshots
    
("Filling in" the Rough Notation forwards, it highlights the first word 3 times in a row)
    Screen Shot 2020-12-28 at 11 55 01 AM
    Here is what the DOM looks like. I'm posting this as evidence that I didn't accidentally notate the same element 3 times, but instead did it to 3 different intervals.
    Screen Shot 2020-12-28 at 12 04 10 PM
    Desktop (please complete the following information):
    • OS: macOS
    • Browser Chrome
    • Version 87.0.4280.88
    Additional context
    
Let me know how I can assist with this bug. I am having trouble understanding what the root cause may be. If someone could help point me in the right direction, that would be greatly appreciated!
    If this ends up being a bug with a library, I would be happy to work on a PR if someone could give me more context on the fix.
    Metadata
    Metadata
    Assignees
    No one assigned
      Labels
      No labels
      No labels
      Projects
      No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions
      
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Drawing notation in wrong location · Issue #17 · linkstrifer/react-rough-notation · GitHub
      Skip to content
      Drawing notation in wrong location #17
      Open
      Open
      Drawing notation in wrong location#17
      Description
      @0x213F
      0x213F
      opened on Dec 28, 2020
      Describe the bug
      
I am rendering multiple RoughNotation elements inline the same component. It looks something like this initially:
      <div>
<span>Hello, my name is </span>
<RoughNotation className={styles.Notated}
show={true}
color="red"
type={modification.type}
animate={modification.animate}>
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

      When the user interacts with the page, they can add more notations. For example, look at the following:
      <div>
<span>Hello, my </span>
<RoughNotation show={true} color="red" type="highlight">
name
</RoughNotation>
<span> is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

      When the new notation occurs before the already established notation, it renders fine (no bug). However, when it renders after, it does not render as expected:
      <div>
<span>Hello, my name is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to </span>
<RoughNotation show={true} color="red" type="highlight">
meet
</RoughNotation>
<span> you!</span>
</div>

      To Reproduce
      
Steps to reproduce the behavior:
      1. Render one Rough Notation inline
      2. Render a second Rough Notation inline, after the first one
      3. See error
      4. You may keep adding Rough Notations ahead of the last one to continue reproducing.
      Expected behavior
      
(I was able to do this by "filling in" the Rough Notations backwards)
      Screen Shot 2020-12-28 at 11 54 14 AM
      Screenshots
      
("Filling in" the Rough Notation forwards, it highlights the first word 3 times in a row)
      Screen Shot 2020-12-28 at 11 55 01 AM
      Here is what the DOM looks like. I'm posting this as evidence that I didn't accidentally notate the same element 3 times, but instead did it to 3 different intervals.
      Screen Shot 2020-12-28 at 12 04 10 PM
      Desktop (please complete the following information):
      • OS: macOS
      • Browser Chrome
      • Version 87.0.4280.88
      Additional context
      
Let me know how I can assist with this bug. I am having trouble understanding what the root cause may be. If someone could help point me in the right direction, that would be greatly appreciated!
      If this ends up being a bug with a library, I would be happy to work on a PR if someone could give me more context on the fix.
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        No labels
        No labels
        Projects
        No projects
        Milestone
        No milestone
        Relationships
        None yet
        Development
        No branches or pull requests
        Issue actions
        
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Drawing notation in wrong location · Issue #17 · linkstrifer/react-rough-notation · GitHub
        Skip to content
        Drawing notation in wrong location #17
        Open
        Open
        Drawing notation in wrong location#17
        Description
        @0x213F
        0x213F
        opened on Dec 28, 2020
        Describe the bug
        
I am rendering multiple RoughNotation elements inline the same component. It looks something like this initially:
        <div>
<span>Hello, my name is </span>
<RoughNotation className={styles.Notated}
show={true}
color="red"
type={modification.type}
animate={modification.animate}>
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

        When the user interacts with the page, they can add more notations. For example, look at the following:
        <div>
<span>Hello, my </span>
<RoughNotation show={true} color="red" type="highlight">
name
</RoughNotation>
<span> is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

        When the new notation occurs before the already established notation, it renders fine (no bug). However, when it renders after, it does not render as expected:
        <div>
<span>Hello, my name is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to </span>
<RoughNotation show={true} color="red" type="highlight">
meet
</RoughNotation>
<span> you!</span>
</div>

        To Reproduce
        
Steps to reproduce the behavior:
        1. Render one Rough Notation inline
        2. Render a second Rough Notation inline, after the first one
        3. See error
        4. You may keep adding Rough Notations ahead of the last one to continue reproducing.
        Expected behavior
        
(I was able to do this by "filling in" the Rough Notations backwards)
        Screen Shot 2020-12-28 at 11 54 14 AM
        Screenshots
        
("Filling in" the Rough Notation forwards, it highlights the first word 3 times in a row)
        Screen Shot 2020-12-28 at 11 55 01 AM
        Here is what the DOM looks like. I'm posting this as evidence that I didn't accidentally notate the same element 3 times, but instead did it to 3 different intervals.
        Screen Shot 2020-12-28 at 12 04 10 PM
        Desktop (please complete the following information):
        • OS: macOS
        • Browser Chrome
        • Version 87.0.4280.88
        Additional context
        
Let me know how I can assist with this bug. I am having trouble understanding what the root cause may be. If someone could help point me in the right direction, that would be greatly appreciated!
        If this ends up being a bug with a library, I would be happy to work on a PR if someone could give me more context on the fix.
        Metadata
        Metadata
        Assignees
        No one assigned
          Labels
          No labels
          No labels
          Projects
          No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Drawing notation in wrong location · Issue #17 · linkstrifer/react-rough-notation · GitHub
          Skip to content
          Drawing notation in wrong location #17
          Open
          Open
          Drawing notation in wrong location#17
          Description
          @0x213F
          0x213F
          opened on Dec 28, 2020
          Describe the bug
          
I am rendering multiple RoughNotation elements inline the same component. It looks something like this initially:
          <div>
<span>Hello, my name is </span>
<RoughNotation className={styles.Notated}
show={true}
color="red"
type={modification.type}
animate={modification.animate}>
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

          When the user interacts with the page, they can add more notations. For example, look at the following:
          <div>
<span>Hello, my </span>
<RoughNotation show={true} color="red" type="highlight">
name
</RoughNotation>
<span> is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

          When the new notation occurs before the already established notation, it renders fine (no bug). However, when it renders after, it does not render as expected:
          <div>
<span>Hello, my name is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to </span>
<RoughNotation show={true} color="red" type="highlight">
meet
</RoughNotation>
<span> you!</span>
</div>

          To Reproduce
          
Steps to reproduce the behavior:
          1. Render one Rough Notation inline
          2. Render a second Rough Notation inline, after the first one
          3. See error
          4. You may keep adding Rough Notations ahead of the last one to continue reproducing.
          Expected behavior
          
(I was able to do this by "filling in" the Rough Notations backwards)
          Screen Shot 2020-12-28 at 11 54 14 AM
          Screenshots
          
("Filling in" the Rough Notation forwards, it highlights the first word 3 times in a row)
          Screen Shot 2020-12-28 at 11 55 01 AM
          Here is what the DOM looks like. I'm posting this as evidence that I didn't accidentally notate the same element 3 times, but instead did it to 3 different intervals.
          Screen Shot 2020-12-28 at 12 04 10 PM
          Desktop (please complete the following information):
          • OS: macOS
          • Browser Chrome
          • Version 87.0.4280.88
          Additional context
          
Let me know how I can assist with this bug. I am having trouble understanding what the root cause may be. If someone could help point me in the right direction, that would be greatly appreciated!
          If this ends up being a bug with a library, I would be happy to work on a PR if someone could give me more context on the fix.
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            No labels
            No labels
            Projects
            No projects
            Milestone
            No milestone
            Relationships
            None yet
            Development
            No branches or pull requests
            Issue actions
            
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Drawing notation in wrong location · Issue #17 · linkstrifer/react-rough-notation · GitHub
            Skip to content
            Drawing notation in wrong location #17
            Open
            Open
            Drawing notation in wrong location#17
            Description
            @0x213F
            0x213F
            opened on Dec 28, 2020
            Describe the bug
            
I am rendering multiple RoughNotation elements inline the same component. It looks something like this initially:
            <div>
<span>Hello, my name is </span>
<RoughNotation className={styles.Notated}
show={true}
color="red"
type={modification.type}
animate={modification.animate}>
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

            When the user interacts with the page, they can add more notations. For example, look at the following:
            <div>
<span>Hello, my </span>
<RoughNotation show={true} color="red" type="highlight">
name
</RoughNotation>
<span> is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

            When the new notation occurs before the already established notation, it renders fine (no bug). However, when it renders after, it does not render as expected:
            <div>
<span>Hello, my name is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to </span>
<RoughNotation show={true} color="red" type="highlight">
meet
</RoughNotation>
<span> you!</span>
</div>

            To Reproduce
            
Steps to reproduce the behavior:
            1. Render one Rough Notation inline
            2. Render a second Rough Notation inline, after the first one
            3. See error
            4. You may keep adding Rough Notations ahead of the last one to continue reproducing.
            Expected behavior
            
(I was able to do this by "filling in" the Rough Notations backwards)
            Screen Shot 2020-12-28 at 11 54 14 AM
            Screenshots
            
("Filling in" the Rough Notation forwards, it highlights the first word 3 times in a row)
            Screen Shot 2020-12-28 at 11 55 01 AM
            Here is what the DOM looks like. I'm posting this as evidence that I didn't accidentally notate the same element 3 times, but instead did it to 3 different intervals.
            Screen Shot 2020-12-28 at 12 04 10 PM
            Desktop (please complete the following information):
            • OS: macOS
            • Browser Chrome
            • Version 87.0.4280.88
            Additional context
            
Let me know how I can assist with this bug. I am having trouble understanding what the root cause may be. If someone could help point me in the right direction, that would be greatly appreciated!
            If this ends up being a bug with a library, I would be happy to work on a PR if someone could give me more context on the fix.
            Metadata
            Metadata
            Assignees
            No one assigned
              Labels
              No labels
              No labels
              Projects
              No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
})();
Drawing notation in wrong location · Issue #17 · linkstrifer/react-rough-notation · GitHub
              Skip to content
              Drawing notation in wrong location #17
              Open
              Open
              Drawing notation in wrong location#17
              Description
              @0x213F
              0x213F
              opened on Dec 28, 2020
              Describe the bug
              
I am rendering multiple RoughNotation elements inline the same component. It looks something like this initially:
              <div>
<span>Hello, my name is </span>
<RoughNotation className={styles.Notated}
show={true}
color="red"
type={modification.type}
animate={modification.animate}>
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

              When the user interacts with the page, they can add more notations. For example, look at the following:
              <div>
<span>Hello, my </span>
<RoughNotation show={true} color="red" type="highlight">
name
</RoughNotation>
<span> is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to meet you!</span>
</div>

              When the new notation occurs before the already established notation, it renders fine (no bug). However, when it renders after, it does not render as expected:
              <div>
<span>Hello, my name is </span>
<RoughNotation show={true} color="red" type="highlight">
0x213F
</RoughNotation>
<span>, nice to </span>
<RoughNotation show={true} color="red" type="highlight">
meet
</RoughNotation>
<span> you!</span>
</div>

              To Reproduce
              
Steps to reproduce the behavior:
              1. Render one Rough Notation inline
              2. Render a second Rough Notation inline, after the first one
              3. See error
              4. You may keep adding Rough Notations ahead of the last one to continue reproducing.
              Expected behavior
              
(I was able to do this by "filling in" the Rough Notations backwards)
              Screen Shot 2020-12-28 at 11 54 14 AM
              Screenshots
              
("Filling in" the Rough Notation forwards, it highlights the first word 3 times in a row)
              Screen Shot 2020-12-28 at 11 55 01 AM
              Here is what the DOM looks like. I'm posting this as evidence that I didn't accidentally notate the same element 3 times, but instead did it to 3 different intervals.
              Screen Shot 2020-12-28 at 12 04 10 PM
              Desktop (please complete the following information):
              • OS: macOS
              • Browser Chrome
              • Version 87.0.4280.88
              Additional context
              
Let me know how I can assist with this bug. I am having trouble understanding what the root cause may be. If someone could help point me in the right direction, that would be greatly appreciated!
              If this ends up being a bug with a library, I would be happy to work on a PR if someone could give me more context on the fix.
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                No labels
                No labels
                Projects
                No projects
                Milestone
                No milestone
                Relationships
                None yet
                Development
                No branches or pull requests
                Issue actions