IE Interprets CSS Differently

This is similar to sharzee's problem, item alignment on a
page, except I am not using a table. I am using CSS to control the
placement of graphics and text boxes on a web page. A sample of the
CSS code is below
.oneColElsCtrHdr #phn-img {
margin: 0;
position: relative;
height: 231px;
width: 200px;
left: 50px;
top: 50px;
padding: 0px;
Both Firefox and Safari display the page with the items where
they should be. IE shows them <b>WAY</b> out of
alignment. Rather than the expected 50 pixels from the Left Margin,
it is closer to 400 pixels from the Left Margin. I have other items
placed with similar coding and all are pushed way too far to the
right in IE. Top positioning is fine.
I had a similar problem with another element and the offset
from where the top was supposed to be. That case was not as extreme
and I was able to get a reasonable compromise in the top
positioning I can live with. I do not want to go back to a table
layout because this page must be readable with screen reader
software and many of those products have trouble with
tables.

This may help you understand positioning a bit -
There are 4 different types of positioning:
Absolute
Relative
Fixed
Static
Here is a brief explanation of each kind of positioning (with
regard to
placement of elements on the page only)....
Position:absolute (or A/P elements)
This does several things -
1. It 'removes' the element from the flow of the code on
the page so that
it can no longer influence the size or position of any other
page element
(except for those contained within it, of course).
2. The absolutely positioned element takes its position from
the position of
its closest PARENT *positioned* element - in the
absence of any explicitly
positioned parent, this will default to the <body> tag,
which is always
positioned
at 0,0 in the browser viewport.
This means that it doesn't matter where in the HTML code the
layer's code
appears (between <body> and </body>), its
location on the screen will not
change (this assumes that you have not positioned the A/P
element within
a table or another A/P element, of course).
Furthermore, the space in
which
this element would have appeared were it not positioned
is not preserved
on the screen. In other words, absolutely positioned elements
don't take
up any space on the page. In fact, they FLOAT over the page.
Position:relative (or R/P elements)
In contrast to absolute positioning, a relatively positioned
page element is
*not* removed from the flow of the code on the page, so
it will use the
spot
where it would have appeared based on its position in
the code as its
zero point reference. If you then supply top, right,
bottom, or left
positions
to the style for this element, those values will be
used as offsets from
its
zero point.
This means that it DOES matter where in the code the
relatively positioned
element appears (, as it will be positioned in that location
(factoring in
the offsets) on the screen (this is true for any placement in
the code).
Furthermore, the space where this element would have
appeared is
preserved in the display, and can therefore affect the
placement of
succeeding elements. This means that the taller a relatively
positioned element is, the more space it forces on the page.
Position:static
As with relative position, static positions also "go with
the flow". An
element with a static position cannot have values for
offsets (top, right,
left, bottom) or if it has them, they will be ignored. Unless
explicitly
positioned, all div elements default to static positioning.
Position:fixed
A page element with this style will not scroll as the page
content scrolls.
Support for this in elements other than page backgrounds is
quirky
There are several other things you need to know:
1. ANY page element can be positioned - paragraphs, tables,
images, lists,
etc.
2. The <div> tag is a BLOCK level tag. This means that
if it is not
positioned or explicitly styled otherwise, a) it will always
begin on a new
line on the screen, and b) it will always force content to a
new line below
it, and c) it will always take up the entire width of its
container (i.e.,
width:100%).
3. The placement of A/P elements *can* affect the BEHAVIOR of
other
elements
on the page. For example, a 'layer' placed over a hyperlink
will mask that
hyperlink.
You can see a good example of the essential difference
between absolute and
relative positioning here -
http://www.great-web-sights.com/gws_layersdemo.php
You can see a good demonstration of why using layers for a
page layout tool
is dangerous here -
http://www.great-web-sights.com/gws_layer-overlap.php
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"PghMitch" <[email protected]> wrote in
message
news:[email protected]...
> Thanks, Walt! I may try this solution tomorrow. My brain
is fried for
> today.
>
> Yeah, it was a little bit of a leap, but since the
relative was being
> questioned, I figured that is where the problem lay, so
I changed to the
> other
> method I knew, absolute.
>
> As I said, I'm just beginning to delve into CSS. I don't
think I could
> wrap my
> mind around static before, as opposed to absolute and
relative. I'm
> chalking
> all this up to the learning curve, so I don't mind
redoing the page again.
> Getting it right will pay huge dividends in the long
run.
>

Similar Messages

V$session and v$sqlarea is interpreting in different way

I am using redhad linux 5 version. The db version is oracle11g.
I am trying to run the below shell script on the linux box
export ORACLE_SID=chf01
export ORACLE_HOME=/ora/app/oracle/product/11.1.0/db_1
export WORKDIR=/ora/app/oracle/admin/chf01/scripts
cd $WORKDIR
$ORACLE_HOME/bin/sqlplus scott/tiger@ch01 << EOF
spool sqlcapture.log
INSERT INTO scott.T_SQL_CAPTURE
SELECT MACHINE,
SQL_FULLTEXT
FROM
v$session a,
v$sqlarea b
where
((a.sql_address = b.address
and a.sql_hash_value = b.hash_value )
or ( a.prev_sql_addr = b.address
and a.prev_hash_value = b.hash_value))
commit;
spool off
exit
EOF
ERROR=`grep 'ORA-' sqlcapture.log | wc -l`
if [ "$ERROR" -gt 0 ]
then
cat sqlcapture.log|mailx -s "sqlcapture is failed" \ [email protected]
else
cat sqlcapture.log|mailx -s "sqlcapture is successful" \ [email protected]
fi
exit
here is the spool file content. v$session is interpreted as v a and v$sqlarea is interpreted as v b.
How can i fix this?
SQL> INSERT INTO scott.T_SQL_CAPTURE
2 SELECT MACHINE,
3 SQL_FULLTEXT
4 FROM
5 v a,
6 v b
7 where
8 ((a.sql_address = b.address
9 and a.sql_hash_value = b.hash_value ) 10 or ( a.prev_sql_addr = b.address
11 and a.prev_hash_value = b.hash_value))
13 ;
v b
ERROR at line 6:
ORA-00942: table or view does not exist
SQL> commit;
Commit complete.
SQL> spool off

Because *$* is interpreted by Linux shell. So you need to escape it. I used to escape all $ with \$ but someone in another thread posted a lovely trick. Use this:
$ORACLE_HOME/bin/sqlplus scott/tiger@ch01 << \EOF
.

Rendering of css different in Firefox vs IE8

I created an external style sheet to define a:link (color light grey), a:visited (light purple), a:hover (light red) and a:active (also light red) to apply to a text and an associated image's border. Firefox renders it correctly but IE8 does not associated the image link with the style sheet; instead it just shows the borders using old blue link color and the purple visited link color, no a:hover or a:active.. What am I doing wrong?

Difficult to see what's wrong, because you only supplied the html, no CSS.
Is there a way for you to upload the pages and provide a link - it's always better to see the page live.
One suggestion is to make sure the links are in this order:
Link; Visited, Hover; Active
LoVeHA (easy way to remember it )
If the image is a link, it will give you a blue box around the image, unless you write a specific style for images that are links.
a img {border: none;} will display no border around a linked image

CSS different borders on all sides

I would like to assign different borders to different sides.
Right now I have this:
border: 1px solid;
border-color: #ddd #fff #ddd #fff;
What I really want is NO boarder at all at the top and
bottom.
Is that possible?
Thank you,
B

No.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Brian" <[email protected]> wrote in message
news:e3t6f2$50a$[email protected]..
> Is there a way to assign these all in one declaration?
>
> Thank you!!!
>
>

CSS different link styles

how can I create different links styles within the same
element?
Can I do something like this?
a {
color: #999;
text-decoration: none;
a:hover {
color: #333;
a:active {
color: #999;
a.style2 {
color: #363;
text-decoration: underline;
font-weight: bold;
a.style2:hover {
color: #333;
a.style2:active {
color: #363;
And then do something like this?
<a class="style2" href="#">Request
Information</a>
Is this legit to do???
Thanks for any help!
Brian

Point well taken, Murray. I like that better.
Shane H
[email protected]
http://www.avenuedesigners.com
"Murray *ACE*" <[email protected]> wrote
in message
news:[email protected]...
> That's not the most efficient way, although it will
work..
>
> The best way would be to use descendent selectors, and
more generic styles
> to avoid repetition, e.g.,
>
> a { styles; } /* this will also hit named anchors if you
have any */
> a:visited { styles; }
> a:hover { styles; }
>
> #secondlinks a { styles; }
> #secondlinks a:visited { styles; }
> #secondlinks a:hover { styles; }
>
> (I have omitted the a:active pseudo-class for
convenience. This method
> will not require the explicit styling of each link the
way Shane's method
> would.
>
> --
> Murray --- ICQ 71997575
> Adobe Community Expert
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
>
http://www.dreamweavermx-templates.com
- Template Triage!
>
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
>
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
>
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
> ==================
>
>
> "Shane H" <[email protected]> wrote
in message
> news:[email protected]...
>> Yes but do it in this order -
>>
>> a:link
>> a:visited
>> a:hover
>> a:active
>>
>> a.style2:link
>> a.style2:visited
>> a.style2:hover
>> a.style2:active
>>
>> etc.
>>
>> --
>> Shane H
>> [email protected]
>>
http://www.avenuedesigners.com
>>
>>
>> "Brian" <[email protected]> wrote in
message
>> news:[email protected]...
>>> how can I create different links styles within
the same element?
>>> Can I do something like this?
>>>
>>> a {
>>> color: #999;
>>> text-decoration: none;
>>> }
>>> a:hover {
>>> color: #333;
>>> }
>>> a:active {
>>> color: #999;
>>> }
>>>
>>>
>>> a.style2 {
>>> color: #363;
>>> text-decoration: underline;
>>> font-weight: bold;
>>> }
>>> a.style2:hover {
>>> color: #333;
>>> }
>>> a.style2:active {
>>> color: #363;
>>> }
>>>
>>>
>>> And then do something like this?
>>> <a class="style2" href="#">Request
Information</a>
>>>
>>>
>>> Is this legit to do???
>>>
>>> Thanks for any help!
>>> Brian
>>
>>
>
>

Published site looks different on mac and pc?

having (finally) published my site, why do the fonts and layout look different on my mac to my husbnad's pc? v odd???

because different browsers interpret CSS files indifferent ways and because fonts that are installed on your mac may not necessarily be installed on your husbands pc. It is a common gripe of web designers (not just those using iWeb) that margins and padding (for example) are all read differently by IE than by FF.

Differing CMYK in Acrobat and Photoshop (same file)

Hi,
I posted this in the Acrobat forum and haven't had a response yet. I am also posting here since it is related to both Acrobat and Photoshop, in case someone in the Photoshop forum can respond. Thanks.
I read different CMYK values for the same PDF file in Acrobat and Photoshop. (Acrobat 9 and Photoshop CS4)
I read the colours in Photoshop after opening the file as 16-bit CMYK. I read the colours for the same PDF file in Acrobat in Output Preview (Point Sample).
Amongst the most noticeable is black:
Photoshop:
C=75%
M=68
Y=67
K=90
Acrobat:
C=0%
M=0
Y=0
K=100
How can that be? Which one to believe?

If your assumption is correct, I don't understand why Photoshop would overrule the CMYK colours in the PDF and interpret them differently, especially since when opening the PDF in Photoshop, I select the CMYK 16-bit option.
Why not? You are merely tagging the objects and force-overriding the color conversion rule based on the original state they were embeded in. Nothing gets ever truly converted in the sense it would in PS. This is merely a way of fixing issues in pre-press and generating the ink plates based thereon and IMO PS is correct in ignoring these device dependent settings and uses its own color management to convert. The way I see it, there is nothing wrong here.
Mylenium

Differing CMYK in Acrobat and Photoshop

I read different CMYK values for the same PDF file in Acrobat and Photoshop. (Acrobat 9 and Photoshop CS4)
I read the colours in Photoshop after opening the file as 16-bit CMYK. I read the colours for the same PDF file in Acrobat in Output Preview (Point Sample).
Amongst the most noticeable is black:
Photoshop:
C=75%
M=68
Y=67
K=90
Acrobat:
C=0%
M=0
Y=0
K=100
How can that be? Which one to believe?

If your assumption is correct, I don't understand why Photoshop would overrule the CMYK colours in the PDF and interpret them differently, especially since when opening the PDF in Photoshop, I select the CMYK 16-bit option.
Why not? You are merely tagging the objects and force-overriding the color conversion rule based on the original state they were embeded in. Nothing gets ever truly converted in the sense it would in PS. This is merely a way of fixing issues in pre-press and generating the ink plates based thereon and IMO PS is correct in ignoring these device dependent settings and uses its own color management to convert. The way I see it, there is nothing wrong here.
Mylenium

Sapscript: Do not interpret two commas in text as tab

Since Sapscript interprets two commas in a row as a tab, this causes a problem for any form which prints out any text containing two commas. Does anyone know a way to get Sapscript to ignore these commas?

Hello friend,
Welcome to SDN.
The interpretation is different.
Situation 1
/: Do,,not,,interpret,,two,,commas,,in,,text,,as,,tab
"the output will look like below text with tabs in between each word.
Do not interpret two commas in text as tab
Situation 2.
"Define two variables in script editor like below and display.
/: DEFINE text1 = 'Do not interpret two,,commas in text as tab'
/: DEFINE text2 = ',,Text will be displayed like this'
/: &text1&,,&text2&
"The output will be like below
Do not interpret two,,commas in text as tab ,,Text will be displayed like this
"It does not care what is there inside program symbols &text1& and &text2&
I think that you will understand.
Thanks
Venkat.O

Layer Opacity percentage from Photoshop is different in After Effects

When importing a layered PS CS3 document into AE CS3 with layers set to different opacity, AE interprets the % differently. AE displays the % as a whole number but when you click on the field you can see the number goes to at least the thousandths.
This is an issue as our animators need to usually make footage loop perfectly and if they use the default imported value as the start value, and then change it over time and then create a new keyframe at the end of the loop to the whole number it displays, it is actually different so there is a slight shift.
As you can see in this example:
PS layer opacity = 10%
AE layer opacity = 10.196%
PS layer opacity = 20%
AE layer opacity = 20%
PS layer opacity = 30%
AE layer opacity = 30.196%
PS layer opacity = 40%
AE layer opacity = 40%
PS layer opacity = 22%
AE layer opacity = 21.0968%
PS layer opacity = 88%
AE layer opacity = 87.8431%
Anyone else know why this is happening? This is a mind boggler for me.
Thanks,
Jon
FYI, our Macs are running:
OS X 10.5.4
AE CS3 8.0.2.27
PS CS3 10.0.1

Simple: AE will use a higher precision than Photoshop even in the 8bpc/16bpc modes, let alone 32bpc. Photoshop will surely use the same values internally, but it doesn't display them. Dunno why, but PS being the old dog it is, I'm not really wondering... More of a question for that forum for sure. Could of course also be a problem with different color profiles/ color space settings between the apps, so this might be worth checking. Maybe you are using an outdated version of a profile in one of them... A simple solution inside AE would be to simply nail down those values with expressions, e.g.
opacity.valueAtTime(thisComp.startTime)
Otherwise: Stay away from the evil Photoshop. ;-)
Mylenium

Color in photoshop different then in aperture

i had to notice that raw files adjusted in aperture always look different in photoshop...
i work in a completely colormanaged environment and i really don't have any problems printing, but when i export files and open them in PS, there is a definite shift in color...
i called apple about this and the answer was that aperture handles and displays color differently then PS does....even with the same colorprofile/space....which does not make a lot of sense to me and i really feel that this wasn't so pronounced a couple of months ago....now my adjustments (especially for skintones) in aperture are almost useless for PS....
during my discussion with the apple tech i also found out that the "edit with PS" option always attaches adobe RGB as the profile, regardless of the setting in the prefs....to work in any other colorspace, one has to export and then manually open in PS....strange but not really a big problem, as long as one knows about it....
what really worries me is the answer i got when i said that the files look very different in aperture and PS...that the 2 apps read and interpret color differently....isn't that what colorsync is all about? or at least should be?
i am looking at my files in aperture using the "onscreen proofing" option set to the colorspace i work in....i have tried to export the same file in different spaces, all with the same result...a visible difference in PS (regardless of the PS working profile or PS soft proofing)....
i am wondering if there is a way to corrupt my colorengine? with several software updates since 10.5 and this seems to get worse? any idea anyone? i keep a clean system and maintain it frequently (and not obsessively) and everything else works great....any input welcome...

I think using the previews (as in quick preview mode) yields results that lie. When making all adjustments, I'm looking at the RAW file.
I think some clarification is needed here for both of you to determine what is going on.
1. Quick Preview Mode uses a jpeg preview that is embedded by the camera within the raw file. It's not "lying". It's just giving you the camera's version of things. Just like Aperture, ACR, DPP, Nikon Capture NX each have different color engines and will give different renderings of the same raw file - the same is happening here. The color and tone of Aperture's Quick Preview Mode is not going to match Aperture's rendering, it will only match the rendering of the OEM software that came with your camera. Quick Preview mode is no different than using something like Photo Mechanic.
2. PSSSSS - your color should be matching between Aperture and a file exported into Photoshop but there are a many variables at play here and you need to pin them down to figure out what is going on.
-I assume you are working on a calibrated display (one calibrated with a hardware device like an Xrite Display or Eye-one or similar). That's the only way to know that what you are seeing is accurate in either program.
-For Aperture, make sure you are not in Quick Preview Mode and you do not have soft-proofing turned on.
-For Photoshop, make sure you do not have "Proof Setup" turned on and in your Color Settings make sure that it is set to "Preserve Embedded Profiles".
-With all three of the above done your color should match. If it does not there another possible issue I'm aware of and that is that Aperture is not compatible with certain kinds of display profiles. This goes back to 2006 and I don't know if it has been corrected. What I found then is that Aperture did not display images correctly if the display/monitor profile uses a "Large (LUT)" setting.
Here's a thread going over that issue:
http://discussions.apple.com/thread.jspa?threadID=469271&tstart=0
I think certain screen calibration pucks like the Huey do use the "Large (LUT)" setting but do not let you know that or give you any other options.
-One last possible issue, PSSSSS, is that your post lists a MacBook Pro as your computer. Are you using an external display? If not there could be an issue in MBP screen and/or its profile. How so? I've found that MBP screen, while the best to date, is still wanting. It can show images as noisy when they are not and it can show images as slightly posterized when they are not. I don't know if this affect is across the board or only within certain programs. For example, when I shoot tethered, my Canon 1DsM3 tethering to my MBP and using Canon's DPP software. The previews in the DPP can look noisy and a touch posterized, as I just mentioned, but the same files opened on my desktop Mac Pro/Apple Cinema Display look just fine.
-In this thread, http://discussions.apple.com/message.jspa?messageID=7518140#7518140 , you mention "Show Master Image" or using the loupe shows a color shift in the image. I'm not seeing that at all on my system. If I remember correctly, this was part of the problem I saw when I found the display profile to be incompatible with Aperture (again, mentioned above).
Jon Roemer
http://www.jonroemer.com
http://jonroemer.typepad.com/

Different colors in Photoshop and Lightroom

A fresh install of LR and PS CS2. I display an image in Lightroom (no adjustments at all) and open it in Photoshop (edit in ps CS2-->edit original). When I skip between LR and PS, I see different colors. The photos displayed in LR seem to be a little bit more saturated than in Photoshop.
What can I do match both photos. So far I am in a situation where I don't know how my photos are going to appear because both programs interpret them differently.

I am having the same problem as Michael... except I am calibrated (and no... I do NOT know the ins and outs of calibration... I do it b/c I am supposed to lol).
*MY* problem is similar to his.... it is ONLY when I have exported pics into PS (CS2 in my case) that I have a problem. LR-only edits are just fine. It is most notably apparent when I choose "export" photos once I am done with them... and once this is done it seems impossible (for me) to undo it!
Everything shifts reddish/magenta/orangey. I also seem to end up with hot spots/blown areas that were not there originally. It is NOT just a monitor issue, as these changes seem to become permanent. But I haven't noticed a desaturated appearance in CS2 (when moving from LR).
I shoot Raw+ Fine jpegs (I like having both for backup purposes) and do all my work on the Raws. I shoot with a Nikon D80, D300, Fuji S5... and have the same problem with all 3 cameras.
My normal workflow is to do a general color correction for all files in LR; choose my 5-10 faves to "showcase" and edit them in CS2 to make them shine more. I always choose "edit copy with LR adjustments" and export them as 8 bit tiffs. After doing my edits I choose Ctrl+S (so it pops back into LR) and then do a fast web copy (from CS2) for my blog. The web copies ALWAYS look great! Now that they are back in LR I don't always notice a problem (or should I say I didn't pay enough attention to them at that point to realize if there was/wasn't an issue) b/c by that time, I was "done" until the ordering process. All that was left was to make the web gallery (via LR).
I vividly remember when I first realized there was a problem... both were sessions where I'd ended up editing almost EVERY picture in CS2 for various reasons. Again, I can't remember if there was a problem once back in LR... but if so, it wasn't very noticeable...
But once I had done a final "export"- EVERYTHING was AWFUL!! And they stayed that way!!! In fact, the more I think about it the more certain I am that they were FINE when they first showed back into LR... b/c I remember seeing everything change and being heartbroken when I couldn't "revert" to the original looking CS2 edits. and they looked even WORSE in LR than online etc.
At first I thought I must have a preset upon export or something odd checked, but I've looked and have found no culprits. Perhaps it is a tiff issue? (I am doing my final exports as jpegs??) but I've seen others complain of the same thing...
all I know is that they look absolutely awful!!! Please give me some guidance!
Here is an example of one of the worst offending galleries of images:
http://gypsyisle.com/denee&will
The CS2 edits were NOT blown out OR red (in fact, I keep that particular monitor a shade bright so that my clients, when viewing on THEIR non-calibrated monitors will not be upset with how light/bright/white everything is! So I don't see how I accidentally blew out so many of these pics and made them red/orange/mageta etc!)

Why are the colors in XTerm (x11) and Apple's terminal are different?

Is there a way to fix this? I would like Apple's terminal to look like XTerm...
the screenshot on the left is X11, and the screenshot on the right is Apple's terminal:

Patrick Collins wrote:
The "Pro" setting and the others are nothing more than settings for background and foreground text. Not the actual ANSI colors found when you do a colorized LS, or syntax highlighting in editors like vim.
So, that is my question, why are these two terminals interpreting colors differently? Where can I FIX what it thinks "blue" is, etc?
OK. I get it now. Apple's blue isn't blue enough I guess. Apparently people have been up in arms over this for years. I guess I missed it.
This hack: http://ciaranwal.sh/2007/11/01/customising-colours-in-leopard-terminal
is supposedly working in 10.6.4 now.

I NEED AN INTERPRETER!!!

Listen I have this problam finding an Interpreter. I'v downloaded the JRE 1.4, 1.3, & 1.2 enviroments but they only seem to install jar files ect...which I might add still dosn't add more sound to my Java Applets. Anyway, Were can I find an interpreter? I'v talk to a guy about it, but he said to download JRE 1.4 Which I already downloaded a couple of days before, but nothing that resembled an interpreter. I was looking up this site one day I found on a search engine, and this guy said "You can find a java Interpreter with JRK from javasoft.com
Now I admit I AM download it right now, but is it an interpreter? Or are there diffrent interpreters out there?
Were do I find a basic interpreter? I'm just another one of those rookies whom has entered his first year into Java & javascript programing. If you have any information, I'd really like to know ^^
Thank you for your time.

It sounds like there has been a mix up.
The guy who told you "You can find a Java interpreter with JRE from javasoft" was correct.
However the interpreter that comes with the JRE is soley for the purpose of interpreting your compiled java code (.class files) into machine runnable code. Thats all it does.
It sounds to me that what you mean by "interpreter" is different from a "Java interpreter".
What do you mean by an "interpreter", and what will you want to use it for ?

Different behavior with aaa configuration

Hi Guys,
Does anyone know if there is any difference in the way the following command is interpreted in different IOS release?
aaa authorization exec default local group <group-name>
I have observed different behaviour with the same set of configuration as foll0w;
- 03.03.05SE on a 3650 switch: here the switch only allow local user to login to the device, the radius user always fails( well unless i change the configuration to xx..default radius local)
- 15.0(2) on 2960: Here i can login both with local user and radius user with the same configuration.
Any thoughts?

Hi,
I would not be surprised specially since the 3560 is running IOS-XE vs the 2960 runs IOS.
HTH

IE Interprets CSS Differently

Similar Messages

Maybe you are looking for