[
https://issues.apache.org/jira/browse/NIFI-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Wicks updated NIFI-6455:
------------------------------
Description:
When editing properties in a scrollable property configuration window, such as
in the Processor Configure window or the Controller Service Configure window.
If the number of properties is too large to fit in the scroll window, than one
(or more?) of the properties will be inaccessible at the bottom. The weird
thing is the scrollbar is the right size, you just can't scroll down that far.
I used GetSolr as my test case, as it has so many properties.
I tested in 1.9.2 and was not able to reproduce the issue, but in 1.10 it shows
up.
was:
When editing properties in a scrollable property configuration window, such as
in the Processor Configure window or the Controller Service Configure window.
If the number of properties is too large to fit in the scroll window, than one
(or more?) of the properties will be inaccessible at the bottom. The weird
thing is the scrollbar is the right size, you just can't scroll down that far.
I tested in 1.9.2 and was not able to reproduce the issue, but in 1.10 it shows
up.
> Can't see config properties that overflow a scrollable list
> -----------------------------------------------------------
>
> Key: NIFI-6455
> URL: https://issues.apache.org/jira/browse/NIFI-6455
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.10.0
> Reporter: Peter Wicks
> Priority: Major
>
> When editing properties in a scrollable property configuration window, such
> as in the Processor Configure window or the Controller Service Configure
> window.
> If the number of properties is too large to fit in the scroll window, than
> one (or more?) of the properties will be inaccessible at the bottom. The
> weird thing is the scrollbar is the right size, you just can't scroll down
> that far.
> I used GetSolr as my test case, as it has so many properties.
> I tested in 1.9.2 and was not able to reproduce the issue, but in 1.10 it
> shows up.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
