Home› Welcome to the FamilySearch Community!› Suggest an Idea

Ongoing problem with visual command boxes like (Life sketch), church said at it here in feedback

LegacyUser
LegacyUser ✭✭✭✭
May 30, 2020 edited September 28, 2020 in Suggest an Idea
Pioneer42 said: Have a case number if any FS rep will take a look to resolve: 06548585 been ongoing for years! I mean literally 5 + years. They never fix this. Its a word wrap issue that needs to be resolved on hyperlinks inside of command boxes that go beyond the page. Dont believe me go look FS. PLEASE FIX. Not just a consideration, it is and always has been a issue, it is a FLAW in programming. Word wrap should stay in the box not go outside of it! Not my side issue either, happens on any computer. It happens in collaboration, like sketch etc...Want a id check the life sketch of this guy, tell me that is not a issue: LZV6-VDJ. Thanks for reading this and fixing if you will.
Tagged:
  • Other
  • Indexing
0
0
Up Down
0 votes

new · Last Updated -

Comments

  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    joe martel said: THe community here does not have access to the information about your case. You may want to escalate your case with support.

    I see the formatting extending outside the lifesketch area because the URL in that free-form text field is really long. A couple options. 
    1. You may want to use a URL shortener. But first, that URL does not resolve to anything at Ancestry.
    2. Create a Source and put a valid URL in the Source URL field, and cite that Source in your lifesketch narrative. 

    The team is aware of the display issue, but not sure it would be very high priority. THanks
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said: Check again, look at visual since you wont go to ID of person I gave in top box:
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said:
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said: Do you understand now?
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said: Do you want others? Doesnt matter where you go, what browser you use, ALL THE SAME Chrome, IE, Edge, Etc...
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said: That is a flaw and a bug
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said: below
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Tom Huber said: No, it isn't.


    Browsers require a separator to break any displayed URL. In the above example, the only separators that are recognized and not interpreted as a space are the "-" and the "?" characters.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    joe martel said: Yes, Thanks. I indicated that it's a display bug and the team is aware.
    Your URL in that lifesketch is broken though and you can do work-arounds as I suggested above.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said: I know its not a high priority, hence the 5 + year battle with this...
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Jeff Wiseman said: Tom,

    I understand what you are saying here regarding the browsers, but from a generic application standpoint, any text box that supports wrapping should be able to force a wrap when normal delimiting characters are not present. Even the dirt-simple TextEdit tool on the Mac has always been able to do this. And even the GetSatisfaction Text editing boxes do it. The following is all one contiguous string of non-delimiting characters:

    lksjdflsjdflskjfljsflskjdflkslfslkdflsjlflskflskdflksflksjfdlksjlfksjlfkjskfsljfklskdjflsjfdlksjfdlksjlfksjdflksjlfjklskfjdlksjflskdjflskfjlskfjlskjflsjflskjflskflskfdlskjlfkjslfkjsljflskfdjlkjslfkjsljfdlskfjlskjflskjflskjflskjdflskjflskjflskfjlsjflksjflkjslfsjfldkjslfjlskjfjlskjflskjfdlsjklfjsljflsjflsjflskjflskjflsjflkjslfjslfjlsjkflskjflskjflsjflsjkflskjflsflskdflskjflskjflsjflsfjlksjflkjsfdlkjsjlfksjdlfkjlsf

    All text boxes supporting wrap in FS should be the same.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Tom Huber said: What FS needs to do is to collapse the URL (like it is done in this forum) when it is too long to be displayed within the expanded field.

    In most instances, that isn't necessarily, but in this instance, the URL is put together by the Ancestry site (which can change, by the way) and so it is displayed with normal browser restrictions.

    Whenever I have a URL from another site (or plan on using a URL, I try to reduce its length to just that required to get to the page I want others to see. In many instances, a URL may have a path displayed that I used to reach that page. I (and others) do not need that path, just the basic URL that will take a person to that location.

    In many instances like this, others will use a shortened URL, such as one created by Bitly. Your non-wrapping URL is https://bit.ly/3gCH8DN using the Bitly site (https://bitly.com/). Note I did not have to pay anything to create the shortened URL.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Tom Huber said: As it stands, your URL does not work because of its length. Neither will the Bitly URL. If you have an ancestry membership, it is entirely possible that it is behind your membership within a tree that you have not shared with the public.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Jeff Wiseman said: Who knows how long bitly.com will be around to support those translations. Do you really want to use that site as a mandatory part of genealogical documentation in the shared tree?
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Jeff Wiseman said: However, I do see this problem, even in GetSatisfaction. Here's a copy paste from Pioneer42's example text:
    ----------------------
    Also READ the source below titled, Notes on Thomas' Non daughter Mary Ford, and also the Way family on the ship register of 1630 and other important info on who her unknown mother is...
    http://interactive.ancestry.com/2496/...

    Posted by Pioneer 41
    -----------------------

    But here is the actual text:

    ----------------------
    Also READ the source below titled, Notes on Thomas&#39; Non daughter Mary Ford, and also the Way family on the ship register of 1630 and other important info on who her unknown mother is... <br> http://interactive.ancestry.com/2496/42521_b158318-00762/46761?backurl=http%3a%2f%2fsearch.ancestry.com%2f%2fcgi-bin%2fsse.dll%3findiv%3d1%26db%3dGreatMigration%26gss%3dangs-d%26new%3d1%26rank%3d1%26msT%3d1%26gsfn%3dthomas%26gsfn_x%3d1%26gsln%3dford%26gsln_x%3dNP_NN_NS%26gskw%3delizabeth%2bchard%26MSAV%3d1%26uidh%3dqup%26pcat%3d40%26fh%3d0%26h%3d46761%26recoff%3d4%2b5%26ml_rpos%3d1&ssrc=&backlabel=ReturnRecord#?imageId=42521_b158318-00762 <br><br> Posted by Pioneer 41
    ------------------------

    So handling these "text boxes" that contain some HTML needs special consideration. Normal text has delimiters in it. URLs do not normally
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Tom Huber said: Jeff, I don't know how long bitly will be around, and so I don't use the feature. Instead, I do what I can to shorten the URL to just the basic parameters needed to reach the page. I have an account with Ancestry and the URL opens my home page. If I am not logged in, it opens the generic home page for those not logged in.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Pioneer42 said: All i can tell you jeff is that they fixed it, and it came back in 2017
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    May 30, 2020
    Tom Huber said: The URL posted by Pioneer42 contains a back URL, which only serves to confuse the URL. That was the URL for the search results, which needed to be modified to just the specific source or whatever was displayed when he picked up the URL. No one can use the URL as it is now constituted, except maybe Pioneer42.
    0
Clear
No Groups Found

Categories

  • 22.6K All Categories
  • 352 1950 US Census
  • 45.9K FamilySearch Help
  • 90 Get Involved
  • 2.3K General Questions
  • 326 Family History Centers
  • 323 FamilySearch Account
  • 3.1K Family Tree
  • 2.5K Search
  • 3.6K Indexing
  • 429 Memories
  • 4.2K Temple
  • 249 Other Languages
  • 28 Community News
  • 5.3K Suggest an Idea
  • Groups