Oct 072015
- NVTRG0 ‘This {post & its comments}’s ‘TOU(Terms Of Use) including copyright ©, confidentiality/privacy, & info’s allowed use’ is JotHere.com’s default TOU(Terms Of Use) except:’ none.
-
NVU9CH a web browser’s tab’s window properly scrolled to & properly highlighting example URL http://1.JotHere.com/4969#NUWMNTNVTRGI post name:
‘‘opening, so web browsing to, ‘a more powerful URL’ used by better websites, especially to some content within a 1.JotHere.com web page ’NVTR95’
- NVTNHD ‘‘section history additional’ ‘in reverse start order’:’ name…
- NVTNHS now originally to next: present.
- NVTNHD ‘‘section history additional’ ‘in reverse start order’:’ name…
- NVTRI9 ‘To reply & discuss, please use JotHere.com’s default methods (click) except:’ none.
- NVTRKV table of contents overall for remainder: ‘definition’ + ‘post history additional’
- NVTN8C ‘definition’: (opening ‘a more powerful URL’)
- NVTKPR is key for every web user to know, including as used by all better websites since the web originated.
- NVTKP0 is fast but tricky, including, do you know the tricks shared in this post?
- NVU2L5 means what the name says
- NVTNDC where ‘a more powerful URL’
- NVV1PG is a URL pointing to 1 or more:
- NVV1RQ a particular location on a page, not just to the whole page
- NVV219 note many URLs and especially these can’t in general be made to be fast retyped by humans (though 1.JotHere’s are near ideal here), so practically must be at least semi-automatically entered.
- NVV1SD to a page requiring being logged in to see its core especially pointed-to content
- NVV1RQ a particular location on a page, not just to the whole page
- NVV1QV is used by all better websites as JotHere, Google docs, GitHub, and many many many more
- NVV1W7 are in use since the web originated (HTML 1.1, so 1990s) thru today
- NVV1PG is a URL pointing to 1 or more:
- NVTNDC where ‘a more powerful URL’
- NVV2Q3 To do it,
- NVUZPX these instructions should be very good, including we’ve carefully made them be complete but still quick for everyone, even for the most beginner web users.
- NVTCXL do these good steps in order:
- NVUT6O follow ‘if you run across most any problem, what to do’
- NVUY3T Know that for most 1.JotHere.com content, the reader can see if s/he got everything right here by the content the web browser highlights & features matches the URL requested, including the frag identifier the content displays: see example image NVU9CH (above)
- NVTLPP Use an standard desktop/laptop web browser, not a mobile OS web browser as they’re buggy here,
- NVTLXE –unless you have time & ability to get the web browser working and/or suffer with it; these steps below will get you started there but it still is often too much trouble.
- NVTCXR Open the URL in your web browser
- NVUXU3 to do so, make sure to exactly copy & enter the URL into to the web browser’s tab’s address bar of what the tab is displaying
- NVUXYE as 1 character wrong or missing or space added will typically totally mess it up and via possibly strange errors.
- NVUY23 How to do this depends on the text display environment:
- NVUXWV In better text display environments, web pages and most email clients, this generally means just clicking on the URL.
- NVUY0J If that doesn’t/won’t work, then try via clipboard copy, which takes only seconds; in order:
- NVUYHQ carefully select the URL, and just the URL (no characters before or after),
- NVUYI1 do copy-to-clipboard (generally Ctrl/Option-C)
- NVUYQR ‘get ready to put in the URL’
- NVUYKQ do clipboard-paste (typically Ctrl/Option-V) which should replace the current URL with this new one.
- NVUYMS press Enter/Return to browse the page
- NVUYNE If that doesn’t/won’t work, then you’ve got a bad situation, so in order:
- NVUYO0 hand copy (via typing) the URL, a bad situation; do in order:
- NVUYP1 do ‘get ready to put in the URL’
- NVUYS4 carefully exactly type the URL
- NVUYSV ‘press Enter/Return to browse the page’
- NVUYTU as time permits, seriously consider getting a better way to {get URLs so they can be readily displayed/opened}
- NVUYWW for instance, if you’re receiving these URLs via SMS/text (very common), then get & use Google Voice or {something better, which I haven’t found}.
- NVUYO0 hand copy (via typing) the URL, a bad situation; do in order:
- NVV2V6 ‘‘section history additional’ ‘in reverse start order’:’
- NVV2W1 inspired by the rentor of recent rental being unable to (the 2nd time) open that URL, from {probably from now trying to hand-copy the URL} plus poor problem handling.
- NVV4PP note you have to wait until opening finishes.
- NVUXU3 to do so, make sure to exactly copy & enter the URL into to the web browser’s tab’s address bar of what the tab is displaying
- NVUZEY wait until that pages finishes loading
- NVTJ6C including without scrolling the page being loaded –unless it is not the case that the URL points a particular location on the page.
- NVUZGO For 1.JotHere.com content, that generally takes ~10 seconds.
- NVUZI1 when done, the web browser’s page-loading indicators will disappear, including, for at least web browser Chrome:
- NVTCTN If the page content displays fine and including there is no password or username prompt (in order to get the content), then skip to the next section, otherwise do in order:
- NVTD1E If the URL you’re opening includes a pointer to a particular portion of the page,
- NVTJDA which is the norm for 1.JotHere.com URLs
- NVTNQS so ends in ‘#’ followed by some alphanumerics, as say ending in #NVTD1E (the link to this point), called a (page-)fragment identifier
- NVTJLN –formerly called a ‘fragment’ in Wikipedia’s URL syntax
- NVTJLW then that portion within the page is what the URL is pointing to
- NVTJMQ then as part of loading the web page, the web browser should scroll that portion into view and ideally highlight it
- NVTJPP which by default web browsers by scrolling the window (tab) so what is being pointed to starts at the top of the window
- NVTJQN which JotHere adds to by
- NVTJXG putting an ideally-bright short vertical outline, currently orange, around else alongside {the ID of the point being anchored to, which it typically floats to the right}
- NVTK0J highlighting the entire content being pointed to.
- NVTKFB –NOT YET but planned as soon as editing tools can be made to support this
- NVTD5D Ensure this happened else does happen (that the portion the URL points to the web browser has highlighted & scrolled into view as described)
- NVTKIP by simplest method: see what the page-fragment identifier refers to has been so scrolled & highlighted
- NVTL93 which on most 1.JotHere.com content is easy, as each piece of content:
- NVTLG3 uses a standard identifier type, so far always a KCGUID (so 6 alphanumeric digits), as ‘NVTLG3‘ for this point.
- NVTLDQ most important, displays its identifier, usually in small OCR-font letters, typically floating it on the right-hand side of the column
- NVTLMX so if you don’t see the identifier where it should be,
- NVTMDX that could be caused by several factors, from the most likely:
- NVTMFH you weren’t logged in before you opened the URL and web browser (or something) has the bug that it doesn’t reattempt the scroll after login
- NVTMK4 Fix is easy: while logged in, just reopen the URL, as again click on it.
- NVTMLU you are using buggy web browser, as many/most mobile browsers
- NVTMZ4 which have bugs as
- NVUARQ ignoring scrolling to the spot or/and
- NVUASH chopping off the page-fragment identifier entirely.
- NVTN1I Fix is, from most preferred:
- NVUAAW use a quality, as desktop/laptop, web browser
- NVUACZ after the page loads, semi-manually find including scroll to the page-fragment identifier by auto-searching for it
- NVUAPL note if it chopped the frag, it takes several second more, as instead you’ll have to in-order:
- NVUAUN go back to the URL you were attempting to open
- NVUAVI if you clicked on a link where the URL is not displayed: on the link, right-click or press-and-hold until a ‘Copy URL (to clipboard)’ option appears which you then select.
- NVUAXW go back the URL’s page (by opening it again or clicking the browser forward button)
- NVUAYP auto-searching for the URL’s frag –note though that the ‘what to search for’ paste will paste in the whole URL which you’ll then have to delete except for the frag identifier.
- NVUAUN go back to the URL you were attempting to open
- NVUAPL note if it chopped the frag, it takes several second more, as instead you’ll have to in-order:
- NVTMZ4 which have bugs as
- NVUAGD you resized or scrolled the window, so the web browser (incorrectly) scrolled the top of the window a new location
- NVUAJ9 fix is: press the browser URL refresh/reload button then wait for reload.
- NVUALW the web browser skipped doing the scroll for reason not listed here (and typically unknown)
- NVUAO3 In Chrome, I find this happens for ~ 1 of 5 URL loads, for reason I don’t know.
- NVUAOZ the fix seems to be 1 to 3 page reload(s)
- NVV00O you mis-typed the URL
- NVV02E you don’t have a good Internet connection. First insure this.
- NVV04X Test this fast & well by ensuring a web page loads {reasonably, so completely & fast-enough}, by either:
- NVV062 browsing else refreshing some page with not too much data but changes, as news.google.com
- NVV1ED on a web page you have open, click on {a link you haven’t visited, so not dimmed out by the browser} which goes to a new page
- NVV04X Test this fast & well by ensuring a web page loads {reasonably, so completely & fast-enough}, by either:
- NVV1KN probably a few more, but rare & TBA later.
- NVTMFH you weren’t logged in before you opened the URL and web browser (or something) has the bug that it doesn’t reattempt the scroll after login
- NVTMF9 just auto-search for the page-fragment identifier in the page, which takes seconds, by just doing in in order:
- NVTM02 in the browser’s URL bar (telling the URL currently displayed), select the page-fragment identifier, then copy it to the clipboard (usually Ctrl/Option-C)
- NVTM2Q Start web-browser page search (Ctrl-F on Windows & Linux, hidden & trickier in Safari (Apple) browser)
- NVTM7F for what to search for, what you copied –paste it (usually Ctrl/Option-V
- NVTMDX that could be caused by several factors, from the most likely:
- NVTLMX so if you don’t see the identifier where it should be,
- NVTNW0 For non- 1.JotHere.com content,
- NVTO2V we won’t go into much detail until later due to our immediate focus on better content so JotHere content.
- NVTNY4 this may be harder, at least to do it universally
- NVTO12 if displaying the fragment identifier in the content is not done
- NVTO07 if the scrolling/highlighting isn’t obvious in itself, one will probably have to look at the page’s HTML source notably by click F12 and Right-click-> Inspector –advanced topics.
- NVTL93 which on most 1.JotHere.com content is easy, as each piece of content:
- NVTKIP by simplest method: see what the page-fragment identifier refers to has been so scrolled & highlighted
-
- NVUVJZ annex
- NVTRIQ ‘post history additional’: ‘‘post history additional’ ‘in reverse start order’:’
- NVV7FM ‘{post.status.snapshot{;date ’20151007Wed1228pst‘;after ID ’minutes 0‘;revision ’1‘;version ’1.0‘;words ’1104‘;as ’small TODOs but need to get it publishd so ‘;do ’Publish 1‘}}’
- NVV747 spellcheck’ {update IDs to latest format: 128 replacements}
- NVV72I TODO: proofread; verify links;
- NVTRF0 update fields then move in drafted content
- NVTQWL ‘{post.status.snapshot: date ’20151006Tue21734pst‘;after ID’ minutes 0‘;revision ’0‘;version ’0.0‘;words ’~300‘;as ’to do that, ‘;do ’minutes ago, to get a reasonable template only (no source text), from http://1.jothere.com/wp-admin/edit.php?post_type=post pick the post with the highest post #, post revision http://1.JotHere.com/5011#NVEAQE , and there do “Copy to a new draft”, so created fresh this post http://1.JotHere.com/5037#NVTR95 then “cut {all its content not to be reused here, so the content just applying to the template, so all the posts’ fully stated points including their KCGUIDs} replacing with new ones.”‘}’.
- NVTQWD but realized beginner users {might be overloaded by all the other detail in that page + may not have scrolling to that location} so best as separate post
- NVTQPH originally drafted at /4670#NVTCFC but
- NVV513 originally motivated {1st use: to keep /8575#NVTC6B short by linking to these details}.
I don’t skim because I’m dyslexic. – I see the last entry was: “if the scrolling/highlighting isn’t obvious in itself, one will probably have to look at the page’s HTML source notably by click F12 and Right-click-> Inspector –advanced topics.”
No comment.