Databases
StackOverflow2013
Postsdbo
POPreventing DOM elements from getting rendered if JS is not enabled
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPreventing DOM elements from getting rendered if JS is not enabled
    primarykey
    data
    text
    <p>Throughout my app, I'd like to use Razor for all functionality related to Reading, and leverage knockoutJS and AJAX for CUD operations. </p> <p>In my profile view, I've done the following:</p> <pre><code>&lt;div&gt; &lt;h4&gt;About Me&lt;/h4&gt; &lt;!-- ko if: !isEditingAboutMe() --&gt; &lt;p&gt;@Model.User.AboutMe&lt;/p&gt; @if (Model.CurrentUserCanEdit) { &lt;a data-bind="click: editAboutMe"&gt;edit&lt;/a&gt; } &lt;!-- /ko --&gt; &lt;!-- ko if: isEditingAboutMe() --&gt; @Html.TextBoxFor(model =&gt; model.User.AboutMe, new { data_bind = "value: aboutMe" }) &lt;a data-bind="click: saveAboutMe"&gt;save&lt;/a&gt; &lt;a data-bind="click: cancelAboutMe"&gt;cancel&lt;/a&gt; &lt;!-- /ko --&gt; &lt;/div&gt; </code></pre> <p>This way search engines can at least crawl the content, and users with javascript enabled can perform CUD operations. The idea is that users with javascript disabled and search engines will get a usable read-only version of the app with no edit capabilities shown.</p> <p>My problem above is that - search engines will see the editing controls since they're wrapped in ko statements. What's the best way to prevent this from happening? </p> <p>One solution I can think of is adding <code>display: none</code> to each of the edit controls and re-enabling it with knockout attribute bindings... thoughts?</p> <p>Also - feedback regarding the "properness" of this approach is welcome.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRobVious
    1. USRobVious
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPreventing DOM elements from getting rendered if JS is not enabled
      1. USRobVious
      1. VTFavorite
    2. VO
      singulars
      1. POPreventing DOM elements from getting rendered if JS is not enabled
      1. USRobVious
      1. VTBountyStart
    1. COHow do you know when a crawler is going to crawl your site? If you knew, and a user was using this page, would you hide these elements and say to the user, "hang on, the site's being crawled and I need to hide some stuff for a minute. BRB"? The `if` binding won't just hide the DOM elements, it removes the elements from the page. Also, there's no need to add/remove the style>display attribute because the `visible` binding will do this for you. This is the subtle difference between the `if` and `visible` binding. `if` adds/removes elements from the DOM and `visible shows/hides elements.
      singulars
      1. POPreventing DOM elements from getting rendered if JS is not enabled
      1. USnwayve
    2. CO@Dennis I don't understand anything in the first part of your comment. And I know the difference between if and visible, that wasn't my question. IF the user has js disabled OR the user is a crawler, I don't want the edit controls on the page. That's the problem I'm trying to solve.
      singulars
      1. POPreventing DOM elements from getting rendered if JS is not enabled
      1. USRobVious
    3. COSorry, I'm just a bit confused about the question. It just sounds like you're trying to hide elements with KO which assumes you've already served up the page to a requester who is either a user or a bot. Isn't this something you would check for before rendering the page and using an @if statement to hide the edit controls? I would probably look at the `Request.UserAgent` string in a controller and perform some Regex to see if the requester is a [bot](http://www.useragentstring.com/pages/Crawlerlist/). Then hide/show elements as appropriate.
      singulars
      1. POPreventing DOM elements from getting rendered if JS is not enabled
      1. USnwayve
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload