Project

General

Profile

Actions

Bug #4481

closed

DHCP server - Dynamic DNS options layout messed up

Added by Kill Bill over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
Start date:
03/01/2015
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.1
Affected Architecture:
All

Description

Actions #1

Updated by Phillip Davis over 9 years ago

services_dhcp.php has not changed since 1 Jan 2015 so should be the same in 2.2
I do not see this problem in 2.2
What browser are you using?

Actions #2

Updated by Kill Bill over 9 years ago

Apparently I was not specific enough. This is in the "DHCP Static Mappings for this interface." -- i.e., when you add a static lease. FF36, Chrome v42, IE11. All messed up. (Latest 2.2.1 snapshots.)

Actions #3

Updated by Phillip Davis over 9 years ago

That made me update my home system to 2.2.1-DEVELOPMENT - time to be checking/testing with that anyway. From Firefox 31.5.0ESR I can add or edit static mappings, click the Dynamic DNS Advanced button and the fields all open out nicely like they should.
Tried on another laptop with Firefox 36.0 and I cannot reproduce the issue there either.

Actions #4

Updated by Kill Bill over 9 years ago

Exact same messed up layout on multiple 2.2 nanobsd boxes. Dunno guys, but I can see obviously missing BR tags on lines 507 and 511 of services_dhcp_edit.php when you compare that with lines 1052/1056 of services_dhcp.php.

Actions #5

Updated by Kill Bill over 9 years ago

Actions #6

Updated by Phillip Davis over 9 years ago

Now I tries with psense_ng_fs theme and can see the problem. That is the different factor. The full screen width is making things like this seen, the text and fields that are missing "br" can actually be rendered on the same line.
Yes, it needs fixing. And you might like to open up lots of GUI pages with pfsense_ng_fs theme and see if there are other places where similar happens.

Actions #7

Updated by Phillip Davis over 9 years ago

I made a pull request to fix that: https://github.com/pfsense/pfsense/pull/1535

Actions #8

Updated by Phillip Davis over 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #10

Updated by Kill Bill over 9 years ago

Fixed, thanks. ;)

Actions #11

Updated by Renato Botelho over 9 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF