From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] zoneconf: reduce the width of inputs for vlanid
Date: Thu, 05 Sep 2019 10:33:36 +0100 [thread overview]
Message-ID: <CB3107AC-931F-423B-90FC-A8EDBA41AF62@ipfire.org> (raw)
In-Reply-To: <d3e12b3e-ecbd-5930-07aa-a6ec8ea3ec4a@starkstromkonsument.de>
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
Hi,
> On 3 Sep 2019, at 19:50, Alexander Koch <ipfire(a)starkstromkonsument.de> wrote:
>
> Hi,
>
> the Problem occurs if you use four zones and the "ipfire-legacy"-Theme. But the "ipfire"-Theme also renders the vlanid-input pretty wide and wraps the line inside the cell. There actually is no need for this, as an VLAN-ID has a maximum length of four digits.
>
> Some Screenshots: https://starkstromlahn.spdns.org/s/qb4iFZmxCQqxb7f
The old theme is practically unmaintainable, but good to take a little bit of care here as well.
Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>
-Michael
>
> Regards, Alex
>
>
> -------- Original Message --------
> From: Michael Tremer [mailto:michael.tremer(a)ipfire.org]
> Sent: Monday, 2 September 2019, 13:32 CEST
> To: Alex Koch <ipfire(a)starkstromkonsument.de>
> Cc: development(a)lists.ipfire.org
> Subject: [PATCH] zoneconf: reduce the width of inputs for vlanid
>
> Hi,
>
> Just for my own illustration, could you send a screenshot?
>
> Best,
> -Michael
>
> On 1 Sep 2019, at 23:47, Alex Koch <ipfire(a)starkstromkonsument.de> wrote:
>
> The inputs for the vlanids are overlapping the borders of their cells (using a recent Firefox on Linux Mint, Android or Windows 7). This patch fixes this by limiting the width to a fixed value.
>
> Signed-off-by: Alex Koch <ipfire(a)starkstromkonsument.de>
> ---
> html/cgi-bin/zoneconf.cgi | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/html/cgi-bin/zoneconf.cgi b/html/cgi-bin/zoneconf.cgi
> index 40239c14e..6b8642818 100644
> --- a/html/cgi-bin/zoneconf.cgi
> +++ b/html/cgi-bin/zoneconf.cgi
> @@ -93,6 +93,10 @@ my $css = <<END
> text-align: center;
> }
>
> + input.vlanid {
> + width: 4em;
> + }
> +
> #submit-container {
> width: 100%;
> padding-top: 20px;
> @@ -432,7 +436,7 @@ foreach (@nics) {
> <option value="NATIVE" $access_selected{"NATIVE"}>$Lang::tr{"zoneconf access native"}</option>
> <option value="VLAN" $access_selected{"VLAN"} $vlan_disabled>$Lang::tr{"zoneconf access vlan"}</option>
> </select>
> - <input type="number" id="TAG $uc $mac" name="TAG $uc $mac" min="1" max="4095" value="$zone_vlan_id" $field_disabled>
> + <input type="number" class="vlanid" id="TAG $uc $mac" name="TAG $uc $mac" min="1" max="4095" value="$zone_vlan_id" $field_disabled>
> </td>
> END
> ;
> --
> 2.17.1
>
>
>
prev parent reply other threads:[~2019-09-05 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 22:47 Alex Koch
2019-09-02 11:32 ` Michael Tremer
2019-09-03 18:50 ` Alexander Koch
2019-09-05 9:33 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CB3107AC-931F-423B-90FC-A8EDBA41AF62@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox