GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Text should contribute to autorange calculations · Issue #2000 · plotly/plotly.js

Text should contribute to autorange calculations #2000

New issue
Copy link
New issue
Copy link
Open
Open
Text should contribute to autorange calculations#2000
Copy link
Labels
featuresomething newsomething new

Description

@RedShift1
RedShift1
opened on Sep 13, 2017
Issue body actions

When drawing a scatter plot with
{ mode: 'lines+markers+text', fill: 'tonexty' }
or
{ mode: 'lines+markers+text', fill: 'tozeroy' }

the text of the first point and the last point is cut off:

plotly_filled

JSFiddle: https://jsfiddle.net/sd7drgph/

Activity

  1. alexcjohnson
    changed the title [-]Text is cut off on the first and last point of a filled scatter plot[/-] [+]Text should contribute to autorange calculations[/+] on Sep 13, 2017
  2. alexcjohnson
    added
    bugsomething brokensomething broken
    on Sep 13, 2017
  3. alexcjohnson commented on Sep 13, 2017

    @alexcjohnson
    alexcjohnson
    on Sep 13, 2017
    Collaborator
    More actions

    Known issue but doesn't look like we have an issue for it - thanks for bringing this up @RedShift1

    I was going to suggest cliponaxis: false #1861 (your leftmost text item would overlap the tick labels but at least would be visible) but I notice that has problems with date axes... another bug report coming :)

  4. alexcjohnson commented on Sep 13, 2017

    @alexcjohnson
    alexcjohnson
    on Sep 13, 2017
    Collaborator
    More actions

    Merging #2001 -> ensure our solution works for both scatter and bar traces.

  5. etpinard
    added
    featuresomething newsomething new
    and removed
    bugsomething brokensomething broken
    on Mar 29, 2019
  6. etpinard commented on Jul 25, 2019

    @etpinard
    etpinard
    on Jul 25, 2019
    Contributor
    More actions

    This would be a nice addition post #2704

  7. chriddyp
    added
    ♥ NEEDS SPON$OR
    on Oct 26, 2020
  8. gvwilson commented on Jun 10, 2024

    @gvwilson
    gvwilson
    on Jun 10, 2024
    Contributor
    More actions

    Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson

  9. gvwilson
    closed this as completedon Jun 10, 2024
  10. emilykl commented on Sep 15, 2025

    @emilykl
    emilykl
    on Sep 15, 2025
    Contributor
    More actions

    still an issue

  11. emilykl
    reopened this on Sep 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featuresomething newsomething new

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.