Project

General

Profile

Actions

Bug #10674

closed

Port Forward Address Fields not becoming active in Safari

Added by Chris Linstruth over 1 year ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Category:
Rules / NAT
Target version:
Start date:
06/18/2020
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:

Description

When you select a method that should allow address/network/alias input in a NAT Port Forward in Safari, the fields are not made active.

Tested in Safari 13.1.1 on macOS 10.14.6.

Screenshot attached.

Thank you.


Files

Actions #1

Updated by Chris Linstruth over 1 year ago

Same on recent 2.5.0.

Actions #2

Updated by Kris Phillips over 1 year ago

Tested working on Firefox. Field updates as expected.

Actions #3

Updated by Steve Beaver over 1 year ago

  • Status changed from New to Assigned
  • Assignee set to Steve Beaver
Actions #4

Updated by Steve Beaver over 1 year ago

  • Status changed from Assigned to Feedback
Actions #5

Updated by Steve Beaver over 1 year ago

  • % Done changed from 0 to 100
Actions #6

Updated by Steve Beaver over 1 year ago

  • Assignee changed from Steve Beaver to Chris Linstruth
Actions #7

Updated by Michael Spears about 1 year ago

Unable to reproduce on Safari 13.1.2 with pfSense 2.5.0.a.20200910.1250

Actions #8

Updated by Chris Linstruth 12 months ago

  • Status changed from Feedback to Closed
  • Target version set to 2.5.0

Looks good in Safari 14.0 on 10.15.7.

Setting as target version 2.5.0 for release notes or cherry-picking if necessary.

Closing.

Actions #9

Updated by Jim Pingle 12 months ago

  • Category changed from Web Interface to Rules / NAT
Actions

Also available in: Atom PDF