Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox Rendering problems #1455

Closed
trafficonese opened this issue Jan 14, 2019 · 2 comments
Closed

Firefox Rendering problems #1455

trafficonese opened this issue Jan 14, 2019 · 2 comments

Comments

@trafficonese
Copy link

This problem started some weeks ago and it is apparently only with Firefox. I also tested Chrome, IE and Edge and they work fine. So I'm not sure if this is the right place to post it.

In the upper part of the plot, some artefacts show up, which seems to happen with geom_col, geom_point, geom_histogram and maybe more. I just checked those functions.

select_arts

Shiny-code:

library(shiny)
library(ggplot2)
library(plotly)

dfN <- data.frame(
  time_stamp = seq.Date(as.Date("2018-04-01"), as.Date("2018-07-30"), 1),
  val = runif(121, 100,1000),
  col = "darkgreen", stringsAsFactors = F
)

ui <- fluidPage(
  plotlyOutput("plt")
)

server <- function(input, output, session) {
  output$plt <- renderPlotly({
    key <- highlight_key(dfN)
    p <- ggplot() +
      geom_col(data = key, aes(x = plotly:::to_milliseconds(time_stamp), y = val, fill=I(col)))
      # geom_point(data = key, aes(x = plotly:::to_milliseconds(time_stamp), y = val, fill=I(col)))
      # geom_histogram(data = key, bins = 10, aes(x = plotly:::to_milliseconds(time_stamp), fill=I(col)))

    ggplotly(p, source = "Src") %>%
      highlight(selectize=F, on="plotly_click", off = "plotly_doubleclick", color = "blue") %>%
      layout(dragmode = "select", xaxis = list(tickval = NULL, ticktext = NULL, type = "date"))
  })
}

shinyApp(ui, server)
@cpsievert
Copy link
Collaborator

Looks like this might be due to a bug in FF itself plotly/plotly.js#3393 (comment)

It'd be much appreciated if you could try with FF 66 when it's released and report back on whether it fixes your issue

@trafficonese
Copy link
Author

It seems to be fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants