The string appears on all <body> tags in some old asp.net webform applications.
VS.NET uses this property to define whether the page (or other container such as Panel control) uses absolute positioning (GridLayout) or not.
I prefer FlowLayout because it works in all browsers AND because it prevents controls from shifting on the page during browser resizes.
In general you should not use grid layout as it does not support browsers with different screen reslutions or font sizes than the one designed on.
They mean nothing to the browser. they are just hints to editing tools. (Visual Studio-Specific)
If i remember right it was used by Visual Studio early on to say whether you wanted to view the design view in Grid or Flow layout mode. I don't think it is used in more current versions and it should have no effect on the browser.
Related
I'm designing a new internal web app that has to support IE11 (as well as Chrome and Firefox). I love doing layouts in Grid, but having to figure out how to make any but the simplest work in IE11 can be a pain. Should I use CSS Grid and ms- prefixes, or avoid the headache and just pass on Grid for this one?
In short, it highly depends on how your application looks like. This article describes the problems you might face quite well - and I fully agree with the summary:
If you are using Grid in a very simple way, and positioning items
rather than using auto-placement then the fact that grid exists in
Internet Explorer from version 10 could turn out very useful. You
could certainly use this in order to create a simpler layout for IE10
and up, once Grid is shipped in other browsers.
However be aware that this is going to require some additional testing
and work, you are unlikely to be able to simply rely on Autoprefixer
to run and do the work for you. For example, if you have used auto
placement for any item and then don’t set a position using the -ms
properties, that item is going to stack up with any other unpositioned
items in the first grid cell.
Today I've learnt something new, that <select> element rendered completely different on a desktop and mobile browser. The problem that I haven't use it before and almost all stuff I've done, is by using Bootstrap's elements.
So my question is actually 2 questions are following:
Why <select> tag rendered differently on mobile chrome and desktop chrome when I debugging in mobile mode? Is it intended behaviour or I can consider it as bug? For example open following page http://www.w3schools.com/tags/tag_select.asp from desktop browser in dev mobile mode and on a hardware device, you will see the difference.
What is the best approach to achieve consistency across various devices? Can I be sure that in all new mobile devices <select> will be rendered "in a mobile way", or just implement my own select element based on Bootstrap modal combined with List group as I've done here: http://codepen.io/anatoly314/pen/EPBmrM?editors=1010 ?
DevTools Device Mode does not emulate mobile-specific UA handling of form elements. This is actually very tricky to do since those things are compiled for that platform build.
The best thing to do is know there will be a difference. In the case of select elements it really doesn't matter much. Since the mobile UX is a full screen scroll selector of the choices.
The absolute best thing, as always, is use Device Mode as a guideline. It is not absolute nor can it be. You will always need to do on-device testing to verify everything works as expected. DM simply gets you 85-90% of the way there without issue.
I have old version of Microsoft Visual Studio.NET (2003) on Windows Server 2003.
I have to manage a Pre-developed database pages. The pages (.aspx) seem to be static and not adjust web page size as per window size of browser and remains aligned towards left. This looks old fashioned.
How can I improve the page by making its size and alignment flexible?
(Note: Unfortunately I can not upgrade any of OS or VS.NET)
you can achieve this by using CSS & You need to apply the css in pecentage and not in pixels then it will be compatible with any browser and also with the mobile.
you will not have to scroll to left or right after applying the proper CSS.
But to achieve this you need to apply proper css to your webpage.
I hope this will solve your problem.
We’ve been looking for reporting components, and we’re having difficulty a report designer that will render reports properly on both phones and computers. We want the report to display in the same way on different screen sizes (desktop and phone), or at the very least, display on both without clipping on the phone. Our thought is the easiest way to lay out such a report is for the report designer to specify table and column sizes as a percent of the width (sort of like HTML tables) rather than hardcoded pixel sizes. So when my page is resized, my report (and content elements) also gets resized, and it continues to fit.
We tried Telerik Reporting but unfortunately they don’t support this feature. They also don’t support the feature where report is resized when window is resized. The size you lay out is the size it is. They indicated they have something that will come out in beta soon, but have given us very few details. We tried the demo for Infragistics, and it seems to have the same limitations.
Is there anything else in the development space that will allow us to produce reports with more “fluid” layout, or in the very least, zoom in on the phone instead of clipping?
is twitter bootstrap an option? tb supports responsive design which will make easier to adapt your report to any device, you just will need to adapt your media queries
kendo ui supports responsive design you may take a look, if bootstrap is an overkill you should try a separate jquery UI or JS library that helps you out with a fluid layout
hope that helps
Greeting,
I have asp.net content page that has more than 30 asp.net controls.
all the control set with style="position:absolute"
I know it is not good practice for ASP.NET web page globalization using style="position:absolute.
Now is there a way to convert my current asp.net page layout to be fit with most of the internet browser.
I read this article http://msdn.microsoft.com/en-us/library/95xdeeha%28VS.90%29.aspx
that explain this issue but it is really hard to go and modify each control.
In case there is no way what I should chnage in my control style propriety to make internet browsers understand the postion of my controls?
THis issue is not specfic to asp.net you should just follow the standard CSS rules and conventions.
There is no automatic tool to convert absolute position items to use relative positioning.
You are going to have to change each component by hand. Best to learn how to layout elements using the margin, padding, float, left, in a relative position to their containing element.
As a first step you must really understand how the box model works see here http://www.html.net/tutorials/css/lesson9.asp