| 2016-07-11 13:15:55 |
ComBin |
description |
Detailed bug description:
See attached screenshot. Customer believes this should be an h5 tag and not h4.
For example: <td class="sortable normal_column"><h4>Medvedev-10.20.31.0</h4><ul><li>10.20.31.12</li></ul><h4>Medvedev-10.20.32.0</h4><ul><li>10.20.32.12</li></ul><h4>Medvedev-10.20.30.1</h4><ul><li>10.20.30.13</li></ul></td>
They see 3 reasons for this:
1. With tag h4 text looks too large, distracting from the overall design;
2. In instances table tag h4 is not used nowhere except that place;
3. There is no objective reason to use this header in this place.
Steps to reproduce:
Associate a floating IP to an instance via Horizon and you will see the private and public networks named in h4 tags.
Expected results:
Should be h5 tags.
Actual result:
h4 tags should be in place.
Reproducibility:
100%
Workaround:
None. AFAIK
Impact:
None. Bug is to fix Horizon for aesthetic reasons.
Description of the environment:
- Operation system: Ubuntu 14.04
- Versions of components: MOS 7.0 |
Detailed bug description:
See attached screenshot. Customer believes this should be an h5 tag and not h4.
For example: <td class="sortable normal_column"><h4>Medvedev-10.20.31.0</h4><ul><li>10.20.31.12</li></ul><h4>Medvedev-10.20.32.0</h4><ul><li>10.20.32.12</li></ul><h4>Medvedev-10.20.30.1</h4><ul><li>10.20.30.13</li></ul></td>
They see 3 reasons for this:
1. With tag h4 text looks too large, distracting from the overall design;
2. In instances table tag h4 is not used nowhere except that place;
3. There is no objective reason to use this header in this place.
Steps to reproduce:
Create new instance connected to two and more networks and you will see name of networks named in h4 tags.
Expected results:
Should be h5 tags.
Actual result:
h4 tags should be in place.
Reproducibility:
100%
Workaround:
None. AFAIK
Impact:
None. Bug is to fix Horizon for aesthetic reasons.
Description of the environment:
- Operation system: Ubuntu 14.04
- Versions of components: MOS 7.0 |
|
