Currently i'm able to create webpart in SharePoint that is allowed to use in full-width mode(manifest:"supportsFullBleed": true). But i need to change some styles accordingly. Is there any way how to identify that webpart is used full-width in code?
SPFx used: 1.15.2
I tried check of width of element, it works in some cases, but when full-width webpart is used in for example mobile than width its not reliable.
The best shot I've seen regarding this may be the "formFactor" context property (it's hidden/not available with type definitions, but actually it exists):
https://learn.microsoft.com/en-us/javascript/api/sp-webpart-base/basewebpartcontext?view=sp-typescript-latest##microsoft-sp-webpart-base-basewebpartcontext-formfactor-member
I have researched this question in numerous places, but I cannot find a definitive answer.
The question in detail is:
I want to import other pages from the SAME domain into EITHER an IFRAME or OBJECT TAG.
It's an html5 website, but I want the OBJECT or IFRAME tag to be searchable and not mess with SEO.
Which one do I use and why?
Which one will work better for IE 6?
basically, (and it pains me to admit) I want to find a way to have one navigation bar that import into one of these tags so i do not need to change them on every page.
There is this stackoverflow question here: Use of Iframe or Object tag to embed web pages in another
BUT it's much older and seems to dismiss html5
I'm trying to avoid:
Server side includes and
JavaScript dependency
Help is GREATLY appreciated!
I have an article set up in Joomla that displays Terms and Conditions for the site users. I would like this to show up in a shadowbox when a user clicks a link. Here is the current anchor text example:
Terms and Conditions
This works out great for displaying the entire web page, but what I would like to do is just display the article text on the page (plain with a white background). Is this in someway possible with shadowbox? If so, how?
If I'm understanding you correctly - you want to suppress the modules and other periphery from your 'page' when it is loaded in the shadowbox.
Add ?tmpl=component to the url of your link.
You can do this with a div element and css shadow effect.
How to show/hide div is explained here:
http://www.randomsnippets.com/2008/02/12/how-to-hide-and-show-your-div/
How you can add shadow is explained here:
http://placenamehere.com/article/384/css3boxshadowininternetexplorerblurshadow/
I believe there are some components to do this - but you may have to get creative to do it without pulling the whole page with an a href tag.
In the database there's a particular area that holds that specifically and you could write a little query to just pull that information specifically and put it in the shadowbox, but what that query would look like I'm not sure.
I am currently designing an e-learning course for a college project. I am using a horizontal spry menu bar. I only have all updated links to other pages on the homepage. All of the rest are empty. I will finish up having more than 140 pages so is there anyway I can update the links from the homepage to work on all pages?
It would save me a huge amount of time.
Thanks.
There are two ways.
The first, and best, way is to call the menu code as some form of include on all pages of your site. You can put the ul structure of the menu system in a separate HTML file and use SSI or any server side language to call it as an include. If you don't have any access to SSI or a server side language, you can make the menu code a Dreamweaver Library Item and call it that way. The benefit here is the menu code exists in one place. Any update to the code will update throughout the site.
The second way is to use Dreamweaver's site-wide find and replace feature to make changes to the menu code on every page of your site.
At the top of many pages in our web application we have error messages and notifications, 'Save' and other buttons, and then our h1 tag with the content title. When making a web application accessible, is it ever acceptable to have content above the top-level structure tag like we do here?
As a screen reader user I don't like content above the main heading. Normally I navigate by headings so would miss the error message. A better solution is to output an h1 heading above the error message, then leave the rest of your headings in tact giving you two h1 headings.
Yes (you can put stuff above them). The H simply means Heading. It's a question of what the heading relates to I guess.
My only caveat is, H2 shouldn't really be above H1, and H3 Shouldn't be above H2. But I don't think it's an actual rule.Websites have menus, warning, notifications. It's acceptable to put them above the rest of your content. I don't see how it would affect accessibility as long as your content is ordered logically. Look at the page CSS turned off. Does it look logical? That's the most important part of accessibility.
Although some people do go that extra mile and have the menu as the last item in the markup and use CSS to bring it back to the top. Personally, I find that solution counter productive. The menu is still important, it belongs at the top of the page.
Yes, just consider it is in that order that the user will get the information. So, if you just did an operation it sounds like a good idea to get any message related to it as the first thing. If it is a notification that appears on any page unrelated to what you are doing, I wouldn't put it above, as it might be a little weird.
Also you can use a text browser that doesn't use styles, it should look like a document with appropriate headers.
Heading tags are used to indicate the hierarchy of the content below it. You should only have one h1 tag and it should be the first content to appear on your page (this is usually the name of the site). Also, you shouldn't skip heading tags when drilling down through different tiers of content.
In your case, you can still use CSS to position items above the h1 tag as long as it is in the correct order in the html.
I assume the elements above the heading are used by JavaScript. In that case, it's preferable if they are created by JavaScript, not included in the source of the page.
To return to your original question, it is probably best that they be at the foot of the page. However, if they are hidden using the CSS "display: none;" or "visibility: hidden;" properties then they will not be seen by most (perhaps all?) screenreaders or by many other assistive technologies, and so should not be an issue. I've written a fairly detailed explanation of why accessibility technology ignores such elements.
Of course if somebody disables CSS things are going to look pretty messy. If there is content on the page that can be used even when CSS and/or JavaScript are disabled, then putting those elements at the bottom of the page will at least make things less cluttered.