spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Leverentz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-28085) Spark Scala API documentation URLs not working properly in Chrome
Date Mon, 22 Jul 2019 17:05:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-28085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890314#comment-16890314
] 

Andrew Leverentz commented on SPARK-28085:
------------------------------------------

This issue still remains, more than a month after the Chrome update that caused it.  It's
not clear whether Google considers it a bug that needs fixing.  I've reported the issue to
Google, as mentioned above, but if anyone else has a better way of contacting the Chrome team,
I'd appreciate it if you could try to get in touch with them to see whether they are aware
of this bug and planning to fix it.

> Spark Scala API documentation URLs not working properly in Chrome
> -----------------------------------------------------------------
>
>                 Key: SPARK-28085
>                 URL: https://issues.apache.org/jira/browse/SPARK-28085
>             Project: Spark
>          Issue Type: Documentation
>          Components: Documentation
>    Affects Versions: 2.4.3
>            Reporter: Andrew Leverentz
>            Priority: Minor
>
> In Chrome version 75, URLs in the Scala API documentation are not working properly,
which makes them difficult to bookmark.
> For example, URLs like the following get redirected to a generic "root" package page:
> [https://spark.apache.org/docs/latest/api/scala/org/apache/spark/sql/Dataset.html]
> [https://spark.apache.org/docs/latest/api/scala/index.html#org.apache.spark.sql.Dataset]
> Here's the URL that I get redirected to:
> [https://spark.apache.org/docs/latest/api/scala/index.html#package]
> This issue seems to have appeared between versions 74 and 75 of Chrome, but the documentation
URLs still work in Safari.  I suspect that this has something to do with security-related
changes to how Chrome 75 handles frames and/or redirects.  I've reported this issue to the
Chrome team via the in-browser help menu, but I don't have any visibility into their response,
so it's not clear whether they'll consider this a bug or "working as intended".



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message