[
https://issues.apache.org/jira/browse/NIFI-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007085#comment-16007085
]
ASF GitHub Bot commented on NIFI-3830:
--------------------------------------
GitHub user scottyaslan opened a pull request:
https://github.com/apache/nifi/pull/1785
[NIFI-3830] force browsers to use URLSearchParams polyfill do to bugs…
… and inconsistent browser implementations
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scottyaslan/nifi NIFI-3830
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1785.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1785
----
commit 9836120c66d83b8cfe2e72c877bf451a8516abe9
Author: Scott Aslan <[email protected]>
Date: 2017-05-11T19:53:43Z
[NIFI-3830] force browsers to use URLSearchParams polyfill do to bugs and
inconsistent browser implementations
----
> Clicking on any component on Linux causes %3F to continuously be added to
> beginning of query string
> ---------------------------------------------------------------------------------------------------
>
> Key: NIFI-3830
> URL: https://issues.apache.org/jira/browse/NIFI-3830
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.2.0
> Environment: Linux
> Firefox & Chromium
> Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0
> (64-bit)
> Firefox 45.1.1
> Reporter: Aldrin Piri
> Assignee: Scott Aslan
> Priority: Minor
> Attachments: malformed query string.png
>
>
> In Debian across both Firefox and Chromium, selecting a component causes
> another %3F (encoded ?) to be prepended to the query string after the
> original ?.
> The URL remains the same until moving up the hierarchy (exiting a process
> group). The UI and URL is still functional but imagine it might cause
> problems should this cause the URL to exceed max length.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
