Cloud DNS should not require the user to manually quote TXT input [136928481]

Assigned

Feature Request

Status Update

No update yet.

Description

le...@mailhardener.com

created issue #1

Jul 8, 2019 02:15PM

When entering a TXT data string into the GCP Cloud DNS input, the user is required to manually quote the TXT data input if they want to retain whitespace. Without quotes, the string is split at whitespace into separate RFC1035 <character-string> objects, which will be concatenated by DNS clients without the whitespace. GCP Cloud DNS effectively strips all whitespace by default, which can cause problems. We believe this is bad UI, because retaining whitespace is what you want in just about any case. In fact, we can't think of any use-case where the current default behavior would even be beneficial.

We (

mailhardener.com) perform security audits for email and have encountered customers that had issues with SPF because GCP unintentionally stripped whitespace from the SPF string.

We would like to propose changing the UI to accept arbitrary strings 'as is' without requiring quoting and retaining whitespace by default.

gcloud_dns_1.PNG

16 KB

View

Download

Comments

se...@google.com <se...@google.com> #2Jul 9, 2019 10:40AM

Assigned to gc...@google.com.

We have passed this to the development team and will update this issue with more information as it becomes available.

go...@gmail.com <go...@gmail.com> #3Jul 16, 2020 07:14AM

Similar problem in my apps when using ScrollView in activities and dialogs. When scrolling up or down there is no animation when we reach the edge. There is no possibility to scroll in the opposite direction until we press the screen. Many apps have this problem. Please fix this issue. Bad user experience.

go...@cheeri.ai <go...@cheeri.ai> #4Jul 16, 2020 07:14AM

Still not fixed in "UPB4.230623.005". Please fix this issue before the final release. Bad user experience in many apps using ScrollView.

sd...@gmail.com <sd...@gmail.com> #5Aug 21, 2020 04:27AM

The issue has been fixed and it will be available in a future build.

do...@google.com <do...@google.com> May 11, 2022 02:05PM

Reassigned to do...@google.com.

le...@mailhardener.com <le...@mailhardener.com> #6May 11, 2022 02:20PM

Unfortunately, this issue has only been partially fixed.

After scrolling the ScrollView content down and then up to the very beginning, the ScrollView content does not return to its starting position. When the screen is pressed again, the ScrollView content returns to its starting position. Same problem when scrolling up and then down to the very end.

Please fix this issue completely before the final release. Bad user experience.

rm...@cerqlar.com <rm...@cerqlar.com> #7Feb 9, 2023 10:26AM

redacted

ju...@coalesce.io <ju...@coalesce.io> #8Jan 16, 2025 03:16PM

For us to further investigate this issue, please provide the following additional information:

Request for you to attach the bug report captured on 4.1 build on the same drive link shared in comment#1. We were not able to reproduce the issue. Thank you. For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice.