StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5478550
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-29T20:30:57.110
FavoriteCount
0
LastActivityDate
2011-03-29T20:30:57.110
LastEditDate
LastEditorUserId
0
OwnerUserId
8409
ParentId
5478165
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<p>I'm having a hard time understanding exactly what your question is, but it looks like Chrome can read <code>.style.display</code> properties just fine. I just threw the following code into an HTML template and loaded it in Chrome 10:</p> <pre><code><div id="div1"> </div> <div id="div2" style="display: block;"> </div> <div id="div3" style="display: inline;"> </div> <div id="div4" style="display: none;"> </div> <script type="text/javascript"> alert(document.getElementById("div1").style.display); alert(document.getElementById("div2").style.display); alert(document.getElementById("div3").style.display); alert(document.getElementById("div4").style.display); document.getElementById("div1").style.display = "none"; alert(document.getElementById("div1").style.display); </script> </code></pre> <p>The code produced 5 'alert' boxes with the following output:</p> <ul><li></li><li>block</li><li>inline</li><li>none</li><li>none</li></ul> <p>So it seems Chome reads this property just fine.</p> <p>Maybe the issue is that the webpage on which you're running your greasemonkey script is behaving differently in Chrome than in Firefox? Could it be that the ID of the element is different, or the element is being removed from the DOM instead of just being hidden? What would happen if you modified your function with some more checks, kinda like this?</p> <pre><code>function readTest() { el = document.getElementById('extra'); if(el) { GM_log(extraFlag); GM_log(el.style.display); if (el.style.display && (el.style.display != 'none') && (!extraFlag)) { alert('extra'); extraFlag = true; } else if ((el.style.display == 'none') || !el.style.display) { extraFlag = false; } } else { GM_log(extraFlag); GM_log("element not present"); extraFlag = false; } } </code></pre> <p>Does that help? If not, is there any other reason you could think of why el.style.display wouldn't evaluate properly in Chrome?</p> <p>It might help if we knew more about what you're trying to do with your script, and possibly what web page or code you're trying to run this on.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POChrome can't read style.display value
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoshua Carmody
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.